Systems and methods for automated derivation of interactive layers for fixed content

ABSTRACT

Systems and methods for implementing fixed-layout display components embedded as part of a screen display of a device. In preferred embodiments, fixed-layout components may be utilized and managed independently of the remaining programmatically generated screen display functionality. A fixed-layout component may comprise a plurality of elements and be associated with user interactivities. Each element may be related positionally, dimensionally and display sequence to an overall component and to other elements comprised such that a computed relative position, size and dimension aspect ratio of component items and the item display sequence is maintained programmatically and visually relative to each other irrespective of a screen size or orientation when the fixed-layout component is part of an overall display of a device. The fixed-layout elements may further be operable to display dynamic data which may be logically associated with data comprised within the overall fixed-layout component.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/489,769 titled, “SYSTEMS AND METHODS FOR INTELLIGENT LAYEREDINTERACTIVE DERIVED PROGRAMMATIC ELEMENTS FOR FIXED CONTENT”, filed onSep. 29, 2021 is a continuation of U.S. patent application Ser. No.17/062,607, titled, “SYSTEMS AND METHODS FOR INTELLIGENT LAYEREDINTERACTIVE DERIVED PROGRAMMATIC ELEMENTS FOR FIXED CONTENT”, filed onOct. 4, 2020, which is a continuation-in-part of U.S. patent applicationSer. No. 16/426,968, titled, “SYSTEMS AND METHODS FOR INTELLIGENTLAYERED INTERACTIVE PROGRAMMATIC ELEMENTS FOR FIXED CONTENT”, filed onMay 30, 2019 which is a continuation of U.S. patent application Ser. No.15/873,905, titled, “SYSTEMS AND METHODS FOR INTELLIGENT LAYEREDINTERACTIVE PROGRAMMATIC ELEMENTS FOR FIXED CONTENT”, filed on Jan. 18,2018 which claims priority to U.S. provisional application 62/447,459,titled, “SYSTEM AND METHODS FOR CREATING AND UTILIZING INDEPENDENTFIXED-LAYOUT DISPLAY COMPONENT(s) FOR SOFTWARE APPLICATION(s) USERINTERFACE AND DEVICE INDEPENDENT”, filed on Jan. 18, 2017. Thedisclosures of all above applications are incorporated herein byreference.

BACKGROUND OF THE INVENTION Field of the Art

The disclosure relates to the field of systems interactivity, and moreparticularly to the field enabling fixed-layout content to receive inputand communication with interactive systems.

Discussion of the State of the Art

Content (text, graphics, photos, images, and/or any combination thereof)may be developed in a wide variety of content or general authoringapplications at present. This content may then be printed or exportedout to a variety of formats depending on the feature/functions of theoriginal source content or authoring user application. This content,which is already authored and available may be required, specifically inbusiness environments, to be re-used in other application softwaresystems or servers comprising database(s), file storage systems,workflow and other logic operations. Various methods may be available toexport out this content from these authoring applications so that it maybe re-used in some way for these other purposes. The content exportapproach from these source/authoring applications may be dependent onthe available functions within these source application which create,and is often typically via an option (a) comprising all the elements attheir lowest level (text, graphics, photos, images, etc.) or via anOption (b) comprising an overall graphic image (i.e. snapshot) whichpreserves the original content layout exactly as it would be presentedvisually to an end user in an associated original source application,via some combination of Option (a) and (b), or via some other processes.If option (a) is available, it may require additional manual efforts toextract and then condition and clean the content so that it isre-useable in the mentioned systems, whereby these manual efforts willresult in additional time and associated cost. If option (b) is used,this will result in fixed-layout content image(s) being exported, and ifthe user then wishes to extract out some or all of the elements (text,graphics, photos, images, etc.), they may need further additionalcontent extraction tools, e.g. optical character recognition (OCR),combined with a plurality of manual efforts to extract and clean theelements for re-use, which results in incurring significantly more timeand cost as compared to option (a). Any further combinations of options(a) and (b), or other derivative methods, may also drive additional timeeffort and cost to complete. Manual time effort and cost problem maybecome a very large problem if the volume of content is high. It istypical for business enterprises to have tens of thousands, if notmillions, of pages of content where there is a pressing requirement tore-use this content in application software and server systems withdatabases, file systems, workflow management systems, and/or other logicsystems as outlined previously, which amplifies the problem. Typicallyreplacing this content into an interactive form requires an unreasonableamount of time and cost, and in some cases, there are mandatoryrequirements to exactly preserve the original content layout precisely(i.e. precise fixed-layout content). Accordingly, many businessenterprises choose option (b) described above, incurring additional timeand huge costs to complete. Fixed-layout content is defined as being aprecise and accurate (for example, pixel by pixel, or using analternative unit of measure) representing the original source authoredcontent.

The above methods are focused on exporting or extracting and orconditioning content for further re-use and combining this with logic toarrive at new systems and server applications, and to deliver new userexperiences for the end user. Accordingly, content extraction,conditioning, and re-use methods, known in the art, incur time and costto complete. Further, some options outlined above provide lessflexibility for content re-use than others in the creation of newapplication processes and systems and servers.

What is needed are systems and methods to easily extract and combineextracted content with programmatic elements to programmatic systems andservers in a way that: (a) significantly reduces time (including manualadditional processes) and associated cost for extraction andconditioning of content; (b) allows for original source content to becombined easily with programmatic element systems and servers; (c)allows separated control and behavior of the extracted content comparedto programmatic elements; (d) allows for easy association ofprogrammatic elements to extracted content; and, (e) supports sizescaling of extracted content such that all associated programmaticelements automatically and dynamically re-size/re-scale relative toother programmatic elements within the extracted content while actingindependently of programmatic system and servers.

SUMMARY OF THE INVENTION

Accordingly, the inventor has conceived and reduced to practice, invarious embodiment of the invention, systems and methods toprogrammatically generate and managing embedded fixed-layoutcomponent(s), and direct associated items or user interactivities into adisplay component of a computer system user interface, that may behaveindependently of other programmatically generated display components. Apreferred embodiment of the invention relates to the use of takingfixed-layout content as discussed in the background to enable re-usablecontent with significantly greater user functionality and reduced timeand associated cost to prepare. Interaction may be received from a userdevice though various elements and associated interactivities that maybe configured as part of these specific component(s). Anetwork-connected component layout computer comprising a processor, adatabase, a memory, and programming instructions stored in the memory,the programming instructions, when executed by the processor maydynamically generate and manage a plurality of fixed-layout componentsthat may be part of a computer system interface whereby the interfacemay behave in a seamless manner when displayed to a user. That is, auser may not notice a difference between fixed and programmaticcomponents. The plurality of fixed-layout components may be independentand may behave independently of the other programmatic elements ofcomputer systems across a range of devices, display sizes, displayorientations, and/or underlying system operating system.

In some embodiments, one or more fixed-layout components may beintegrated within online or native installed user device applicationsexecuting on a display of a computing system. In some embodiments, theremay be many fixed-layout content components embedded in the overall userinterface display.

The one or more fixed-layout components, and direct associated items maybe linked to each other (within the component) via associated dimensionsand positional data and may be collectively referred to hereinafter asreferred to as, “component”.

In some embodiments, one or more fixed-layout components and directassociated elements may proportionally re-scale, in size, exactly andrelative to each other, depending on the screen size of a user interfacedisplay of a target computer device; and may be independent of otherre-scaling and re-alignments performed by remaining elements of the userinterface.

An embedding approach for fixed-layout components and direct associateditems may provide an additional method of building a component of acomputer system user interface that may be then seamlessly embedded intoan overall programmatic derived user interface display. Thisfixed-layout component inclusion in a user interface provides analternative and fast method to having to programmatically recreatecontent elements in a manner (for example, from digital print media)that may exactly replicate, including aspect ratio, positional data,original content item, and which may behave independently of theprogrammatic display for a user device or orientation. Direct associatedelements may then be directly linked to this fixed-layout component foradditional user visual presentation and additional interactions receivedfrom user devices. In some embodiments, direct associated elements mayalso support interactions received from a user device with an ability toreceive user-entered data that may then be re-associated with the one ormore fixed-layout components.

In some embodiments, the user interface comprising the fixed-layoutcomponent and the direct associated elements may be displayed on acomputing device for example, via an online application or a nativedevice installed application, and an associated one or more fixed-layoutcomponents and associated elements may present a same proportion,position, and dimension, independently of properties (size, display,orientation, etc.) of the user device.

Exemplary embodiments of the systems and methods described hereincomprise generation of one or more fixed-layout components, assemblage,and usage of the components while providing reliance on positional anddimensional (and other data types) for at least a portion of the itemscomprised within each fixed-layout component.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings illustrate several embodiments of theinvention and, together with the description, serve to explain theprinciples of the invention according to the embodiments. It will beappreciated by one skilled in the art that the particular embodimentsillustrated in the drawings are merely exemplary and are not to beconsidered as limiting of the scope of the invention or the claimsherein in any way.

FIGS. 1A and 1B illustrate an exemplary user device screen detailing theprogrammatic display area and an embedded fixed-layout componentdisplay, according to an embodiment of the invention;

FIGS. 2A and 2B illustrate an exemplary expanded view of a fixed-layoutdisplay component, according to an embodiment of the invention;

FIG. 3 illustrates an exemplary definition of dimensions of a pluralityof fixed-layout component according to an embodiment of the invention.

FIG. 4 illustrates an exemplary definition of dimensions of a pluralityof element items areas that may be part of a fixed-layout componentdisplay, according to an embodiment of the invention;

FIGS. 5A and 5B illustrate an example of positional dimensions of anelement area in relation to a defined reference location on an overallfixed-layout component area, according to an embodiment of theinvention;

FIGS. 6B and 6B illustrate examples of different reference positionlocation for a plurality of elements and a reference position locationfor the overall fixed-layout component area, according to an embodimentof the invention;

FIGS. 7A and 7B illustrate an example of interactivity between elementareas and calculation of position and dimensions, according to anembodiment of the invention;

FIG. 8A illustrates an example of the various data stores associatedwith items as part of one or more fixed-layout area display components,according to an embodiment of the invention;

FIG. 8B illustrates an example of the various data stores (including theVariable Rules) associated with items as part of one or morefixed-layout area display components, according to an embodiment of theinvention;

FIG. 9 is a high-level flow diagram illustrating an exemplary processfor calculation of dimension data for items which may be part of afixed-layout component area, according to an embodiment of theinvention;

FIGS. 10A, 10B, and 10C illustrate an example of a fixed area windowwhich may be part of the overall user programmatic display window in adisplay screen, according to an embodiment of the invention;

FIG. 11 illustrates a plurality of exemplary fixed-layout windows and acomponent comprised therein as it is repositioned and automaticallyresized in various device screens sizes, according to an embodiment ofthe invention;

FIG. 12 illustrates various examples of a fixed-layout window and afixed-layout component comprised inside a display screen as it isrepositioned and resized according to one specific device screens indifferent orientations, according to an embodiment of the invention;

FIG. 13 illustrates an exemplary interaction between a user deviceinteracts and a server system in the context of an online connectedsoftware program, according to an embodiment of the invention;

FIG. 14 illustrates an exemplary interaction between a user devicecomprising a full application program and an online server system,according to an embodiment of the invention;

FIG. 15 is a high-level flow diagram illustrating an exemplary processfor programmatically loading and displaying a plurality of andfixed-layout components, according to an embodiment of the invention;

FIGS. 16A and 16B illustrate an exemplary embodiment of a fixed-layoutcomponent combined with programmatic display elements on a tablet userdevice screen with a plurality of orientations, according to anembodiment of the invention;

FIG. 16C illustrate another exemplary embodiment of a fixed-layoutcomponent combined with programmatic display elements on a mobile devicewith interactive variable components, according to an embodiment of theinvention;

FIGS. 17A and 17B illustrate exemplary system components which may beused with the system, according to an embodiment of the invention;

FIG. 18A illustrates an exemplary embodiment of a fixed-layout componentwhich may comprise a fixed-layout content background area, and anynumber of digital graphics (to make up a full or partial area), visualitems (text, pictures, etc.), that may comprise a plurality ofhighlighted areas embedded as part of any number of digital graphics,according to an embodiment of the invention;

FIG. 18B illustrates an exemplary embodiment of fixed layout componentwhich may comprise a fixed-layout content background area, and anynumber of digital graphics (to make up a full or partial area), visualitems (text, pictures, etc.), that may comprise a plurality ofhighlighted areas embedded as part of any number of digital graphics,and wherein a new derived element area is illustrated, according to anembodiment of the invention;

FIG. 18C illustrates another exemplary embodiment of a fixed-layoutcomponent comprising the fixed-layout content background area, one ormore digital graphics, visual items that may comprise one or morehighlighted areas embedded as part of any number of digital graphics,and computations of one or more derived areas, according to anembodiment of the invention;

FIG. 18D illustrates another exemplary embodiment of a fixed-layoutcomponent comprising the fixed-layout content background area, one ormore digital graphics, visual items that may comprise one or morehighlighted areas embedded as part of any number of digital graphics,and wherein derived areas examples are shown, according to an embodimentof the invention;

FIG. 18E to 18G illustrates exemplary embodiments of a fixed-layoutcomponent comprising the fixed-layout content background area, one ormore digital graphics, visual items that may comprise one or morehighlighted areas with different borders embedded as part of the one ormore digital graphics, and wherein derived areas are found and shownaccording to various embodiments of the invention;

FIG. 18H illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, and wherein a found element area is spread across differentareas in the background area, according to an embodiment of theinvention;

FIG. 18I illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, whereby the highlighted areas comprise at least one bordercoinciding with an edge of the fixed-layout component, according to anembodiment of the invention;

FIG. 18J illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, further comprising different derived area calculations wherebyone or more border edges are shown, further comprising differentsettings for calculated derived areas, according to an embodiment of theinvention;

FIG. 18K illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, further comprising variable label items on the backgroundarea, and with linked variable data items displayed within the displayproperties of found or derived areas in a layer on the background areaaccording to an embodiment of the invention;

FIG. 19A is a high-level flow diagram illustrating an exemplary processfor an automatic finding and calculation of element item areas andassociated data for data stores, according to an embodiment of theinvention;

FIG. 19B is another high-level flow diagram illustrating anotherexemplary process for an automatic finding and calculation of found orderived element (or both) item areas using configurable search logic andwith associated data for data stores, according to an embodiment of theinvention;

FIG. 20 is a block diagram illustrating an exemplary hardwarearchitecture of a computing device used in an embodiment of theinvention;

FIG. 21 is a block diagram illustrating an exemplary logicalarchitecture for a client device, according to an embodiment of theinvention;

FIG. 22 is a block diagram showing an exemplary architecturalarrangement of clients, servers, and external services, according to anembodiment of the invention;

FIG. 23 is another block diagram illustrating an exemplary hardwarearchitecture of a computing device used in various embodiments of theinvention;

FIG. 24A is a block diagram illustrating an exemplary systemarchitecture for exporting fixed-layout content items and associateddata stores, according to an embodiment of the invention;

FIG. 24B is another block diagram illustrating an exemplary systemarchitecture for exporting fixed-layout content items and associateddata stores, according to an embodiment of the invention;

FIG. 25 is a flow diagram illustrating an exemplary process for findingand automatically configuring element areas (single areas and arearanges) that are outlined on or in fixed-layout content items andassociated data stores, according to an embodiment of the invention;

FIG. 26A is a flow diagram illustrating an exemplary process forlayering additional objects, or object areas, over fixed-layout contentitems and associated data stores, according to an embodiment of theinvention;

FIG. 26B is a flow diagram illustrating another exemplary process forlayering additional objects, or object areas, over fixed-layout contentitems and associated data stores, configuring found and derived elementareas, and configuring specific search logic, according to an embodimentof the invention;

FIG. 27A is a flow diagram illustrating an exemplary process forautomatically finding an element area inside a figure outline which isembedded in a fixed-layout content item, according to an embodiment ofthe invention;

FIG. 27B is a flow diagram illustrating another exemplary process forautomatically finding an element area inside a figure outline which isembedded in a fixed-layout content item using configurable search logic,according to an embodiment of the invention;

FIG. 28 is a block diagram illustrating an exemplary process forretrieving and displaying fixed-layout components as part of overallapplication systems, according to an embodiment of the invention.

FIG. 29 is a flow diagram illustrating an exemplary process forautomatic processing of data rules associated with found or derivedelement areas, according to an embodiment of the invention.

DETAILED DESCRIPTION

The inventor has conceived, and reduced to practice, systems and methodsof programmatically generating and managing a plurality of embeddedfixed-layout components and associated items into a display component ofa computer system user interface.

One or more different inventions may be described in the presentapplication. Further, for one or more of the inventions describedherein, numerous alternative embodiments may be described; it should beappreciated that these are presented for illustrative purposes only andare not limiting of the inventions contained herein or the claimspresented herein in any way. One or more of the inventions may be widelyapplicable to numerous embodiments, as may be readily apparent from thedisclosure. In general, embodiments are described in sufficient detailto enable those skilled in the art to practice one or more of theinventions, and it should be appreciated that other embodiments may beutilized and that structural, logical, software, electrical and otherchanges may be made without departing from the scope of the particularinventions. Accordingly, one skilled in the art will recognize that oneor more of the inventions may be practiced with various modificationsand alterations. Particular features of one or more of the inventionsdescribed herein may be described with reference to one or moreparticular embodiments or figures that form a part of the presentdisclosure, and in which are shown, by way of illustration, specificembodiments of one or more of the inventions. It should be appreciated,however, that such features are not limited to usage in the one or moreparticular embodiments or figures with reference to which they aredescribed. The present disclosure is neither a literal description ofall embodiments of one or more of the inventions nor a listing offeatures of one or more of the inventions that must be present in allembodiments.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only and are not to betaken as limiting the disclosure in any way.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or morecommunication means or intermediaries, logical or physical.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Tothe contrary, a variety of optional components may be described toillustrate a wide variety of possible embodiments of one or more of theinventions and in order to more fully illustrate one or more aspects ofthe inventions. Similarly, although process steps, method steps,algorithms or the like may be described in a sequential order, suchprocesses, methods and algorithms may generally be configured to work inalternate orders, unless specifically stated to the contrary. In otherwords, any sequence or order of steps that may be described in thispatent application does not, in and of itself, indicate a requirementthat the steps be performed in that order. The steps of describedprocesses may be performed in any order practical. Further, some stepsmay be performed simultaneously despite being described or implied asoccurring non-simultaneously (e.g., because one step is described afterthe other step). Moreover, the illustration of a process by itsdepiction in a drawing does not imply that the illustrated process isexclusive of other variations and modifications thereto, does not implythat the illustrated process or any of its steps are necessary to one ormore of the invention(s), and does not imply that the illustratedprocess is preferred. Also, steps are generally described once perembodiment, but this does not mean they must occur once, or that theymay only occur once each time a process, method, or algorithm is carriedout or executed. Some steps may be omitted in some embodiments or someoccurrences, or some steps may be executed more than once in a givenembodiment or occurrence.

When a single device or article is described herein, it will be readilyapparent that more than one device or article may be used in place of asingle device or article. Similarly, where more than one device orarticle is described herein, it will be readily apparent that a singledevice or article may be used in place of the more than one device orarticle.

The functionality or the features of a device may be alternativelyembodied by one or more other devices that are not explicitly describedas having such functionality or features. Thus, other embodiments of oneor more of the inventions need not include the device itself.

Techniques and mechanisms described or referenced herein will sometimesbe described in singular form for clarity. However, it should beappreciated that particular embodiments may include multiple iterationsof a technique or multiple instantiations of a mechanism unless notedotherwise. Process descriptions or blocks in figures should beunderstood as representing modules, segments, or portions of code whichinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Alternate implementations areincluded within the scope of embodiments of the present invention inwhich, for example, functions may be executed out of order from thatshown or discussed, including substantially concurrently or in reverseorder, depending on the functionality involved, as would be understoodby those having ordinary skill in the art.

The following description is presented to enable any person skilled inthe art to make and use the present invention and is provided in thecontext of various embodiments and their requirements. Variousmodifications to the disclosed embodiments will be readily apparent tothose skilled in the art, and the general principles defined herein maybe applied to other embodiments without departing from the spirit of thescope of present embodiments. Thus, the invention is not limited to theembodiments shown, but the present embodiments are to be accorded thewidest scope consistent with the principles and features disclosedherein.

The disclosed technology and methods address the need in the art forcreating and utilizing fixed-layout component package(s) which may thenbe embedded in the overall programmatic user device interface to createone overall interaction for the user. Certain embodiments of the presentinvention relate to how fixed-layout display component(s) may becreated, embedded and managed across a wide range of user devices anddevice types, and where component(s) may be displayed consistently (e.g.aspect ratio, positioning, display layer sequence etc.) irrespective ofthe device type and orientation, and which is independent of the overallprogrammatic display user interface. The user may interact with dataelements which may be comprised within the fixed-layout component andwhich are linked positionally to the underlying fixed-layout componentlayout area via the defined component specific data. The fixed-layoutarea component may be resized and repositioned across any device ororientation and where the component(s) may then display in a sameconsistent manner irrespective of the device screen size or orientationor user viewing area.

Definitions

Found element, as used herein, refers to an area in a fixed layout thathas been found by an intelligent layering computer comprising at least aprocessor 41, a memory 43, and a plurality of programming instructionsstored in the memory 43 and operating on the processor 41, theprogramming instructions, when executed by the processor, cause theprocessor to find element areas within a fixed-layout componentcomprising dimensional, positional, and display-layer data may then bereferred to as element items.

User Display Layout Examples

FIG. 1A illustrates an exemplary user device screen detailing theprogrammatic display area and an embedded fixed-layout componentdisplay, according to an embodiment of the invention. According to theembodiment, device overall display area 100 may comprise fixed-layoutdisplay area component 102, and an area of screen 103 which is generatedprogrammatically. The resulting overall user interface may be acombination of fixed-layout component(s) and programmatic elements.

FIG. 1B illustrates an exemplary user device screen detailing the devicescreen 104, the programmatic display area 110, and a number of embeddedfixed-layout components 106, 107, 108, 109 displayed, according to anembodiment of the invention.

FIG. 2A illustrates an exemplary expanded view of a fixed-layout displaycomponent, according to an embodiment of the invention. According to theembodiment, fixed-layout display component 102 may be an enlarged viewof 102 (referring to FIG. 1A). This fixed-layout component 102 maycomprise fixed-layout component elements; area 201, and any number ofassociated fixed-layout element item 202, 203, 204, 205, 206, 207, 208.The fixed-area component element areas 202, 203, 204, 205, 206, 207,208, may be fixed positionally relative to the overall area of componentarea 201, and therefore relative to at least a portion of othercomponent elements referenced. The fixed-layout element areas may becomprised within the fixed area content item 201, or any programmableshape area, including rectangles, triangles, circles, and/or othershapes which may be overlaid on top of area 201. Each fixed-layoutelement area 202, 203, 204, 205, 206, 207, 208 may comprise one or manycontent items (e.g. images). The component area 201 which is visible(that is, not hidden from view by the element areas) may have aprogrammable generated user interactivity (e.g. data text entry,selection, etc.). Elements areas 202, 203, 204, 205, 206, 207, 208 mayhave a plurality of programmable generated user interactivityassociations. Programmable interactivities allows additional functionson overall component area 201 or on any element 202, 203, 204, 205, 206,207, 208 which may be associated with the overall component 102, or anycombination thereof.

FIG. 2B illustrates another exemplary view of a fixed-layout displaycomponent, according to an embodiment of the invention. According to theembodiment, fixed-layout component 102 (referring to FIGS. 2A and 2B)may be an enlarged view of 102 in FIG. 1A. The component 102 maycomprise fixed-layout component area 201, which may comprise any numberof fixed-layout element items 211, 212, 213, and 214. According to theembodiment, the fixed-layout element items 211, 212, 213 may bepartially overlapping with each other. Each fixed-layout area (that is,the overall area 201, and elements 211, 212, 213, 214) may each beassociated with relevant display-layer identifier data. Thedisplay-layer identifier data may be used when the overall fixed-layoutcomponent is being displayed in a user device screen 101 (referring toat least FIG. 1A) to determine the display order or sequence of thevarious areas for display within the component. The display-layeridentifier data may determine areas that may be visible on an interfacedisplay (for example, of a user device) and which may be partially orfully hidden from direct view (for example, by a user via the userdevice), as illustrated in FIG. 2B. Further according to the embodiment,overall area 201 may have, for example, a display-layer identifier=1,and area 213 and 214 may have, for example, a display-layeridentifier=same as each other=2, and area 212 may have, for example, adisplay-layer identifier=3, and area 211 may have, for example, adisplay-layer identifier=4.

Dimensions General Definition

In some embodiments, at least a portion of dimensions relating to afixed-layout component may be related to digital-imaging ordigital-content and may be measured or represented in a pixel, pel, dotsor picture element or other related methods for dimensions. Themeasurement types may, in some embodiments, relate to a physical pointin a raster image, or to a smallest addressable element. Forconvenience, the term pixels as the exemplary definition of a dimensionwill be used hereinafter but noting that a wide range of other methodsmay also be used to achieve a similar or the same result.

For convenience, pixels may be normally arranged in a regulartwo-dimensional grid. The location of co-ordinates address (or otherexemplary method) of a pixel will correspond to its physical coordinateswithin this dimensional area. All dimensions referenced may relate to atwo-dimensional view.

FIG. 3 illustrates an exemplary definition of dimensions of a pluralityof fixed-layout component according to an embodiment of the invention.According to the embodiment, fixed-layout component 102, fixed-layoutcomponent are 201, detailing width 301 and height 302 dimensions may beused to derive a fixed-layout component aspect-ratio (dimension width301 divided by dimension height 302) and which may always be used in thedisplay/redisplay of this fixed-layout component area across anydevice/screen and to ensure that the calculated aspect-ratio is what mayalways be displayed in user device screen 101, irrespective of theactual aspect ratio or orientation of a physical screen associated touser device 101.

FIG. 4 illustrates an exemplary definition of dimensions of a pluralityof element items that may be part of a fixed-layout component display,according to an embodiment of the invention. According to theembodiments, fixed-layout component 102, with the fixed-layout componentarea 201. FIG. 4 further illustrates component element fixed area 207detailing element width 401 and element height 402 dimensions and whichmay be used to derive a component element aspect-ratio (that is,dimension width 401 divided by height 402) which may be used indisplay/redisplay of this fixed-layout element across any device/screenas part of specific fixed-layout component 102.

FIG. 5A illustrates an example of positional 2D dimensions of an element207 in relation to a defined reference location 509 on an overallfixed-layout component area, according to an embodiment of theinvention. According to the embodiment, an exemplary method to calculatethe dimensional data for elements within a component and which measurethe elements size and position precisely in relation to the overallcomponent area 201 is shown. According to the embodiment, an exemplarymethod to use 2D dimensional x and y axis methodology to determinespecific x-y coordinates is also presented.

In FIG. 5A, the fixed-layout component reference point 501 may be anyfixed location associated to component area 201. Component area 201 mayhave associated dimension x-Axes 502 and y-Axes 503 and direction.Accordingly, each fixed-layout element may have an associated referencepoint in a two-dimensional dimension display grid which may have anx-Axis 502 and a y-Axis 503. Each Axes may each have dimensional valuesfrom 0, 1 (506) to “n” (507) as for the x-Axis and from 0, 1 (504) to“n” (505) as shown for the y-Axis. Each dimension point will have an xand y dimension pair value in the x-y two-dimensional dimension grid.Further according to the embodiment, element area 207 may haveassociated reference point 509 displayed which may have a unique x and yco-ordinate pair values for dimension position. In this embodiment, thecomponent reference point 501 may have a position of 0, 0 for the x, ydimension's pair. Element 207 may be positionally and dimensionallyrelated to the component reference point 501 via the element referenceheight 508 and the element reference width 510 dimensions. The element207 may have a fixed dimension size for width and height 401, 402 andposition 508, 510, relative to the overall component area 201, and withsize/area 301, 302. Dimension values may be derived from thecorresponding x and y co-ordinate position pair dimension values of atleast a portion of all corner points for the overall component area andassociated element areas (for the element type shown: rectangle areas).The x and y coordinate values for the element area 207 corner points509, 511, 512, 513 may be used to derive the element width and heightdimensions as well as area and the position of the area relative to theoverall fixed-layout component area. It should be understood by thosewith ordinary skill in the art that alternate methods may be used toarrive at the same feature, functionality, or conclusion.

FIG. 5B illustrate an exemplary variation of positional dimensions of anelement in relation to a defined reference location on an overallfixed-layout component area, according to an embodiment of theinvention. According to the embodiment, an exemplary variation of FIG.5A is shown with respect to the y-Axis dimension 511 orientation, ascompared to the y-Axis 503 as demonstrated in FIG. 5A. However, theremay be many other different approaches to measuring the variousdimensions required to deliver a same required result of maintaining thepositional and area and size integrity of at least a portion of allitems relative to each other, and in relation to the overall componentarea, and which are part of each specific fixed-layout component 201.

FIG. 6A illustrates an example of a reference position location for aplurality of elements and a reference position location for the overallfixed-layout component area, according to an embodiment of theinvention. According to the embodiment, how each element reference point502, 601, 602, 603, 604, 605, 606 may be connected, and referenced backto the component reference point 501 via the reference height 503, andreference width 504 of each element may be shown.

FIG. 6B illustrates an example of a different reference positionlocation for a plurality of elements and a reference position locationfor the overall fixed-layout component area, according to an embodimentof the invention. According to the embodiment, element reference points607, 608, 609, 610, 611, 612, 613 may be positioned centrally in eachcomponent element. It should be understood by those experienced in theart that alternate methods could be used to arrive at the same feature,functionality, or conclusion.

FIG. 7A illustrates an example of interactivities (including displayproperties) provided by the element areas to an embodiment of theinvention. According to the embodiment, example element areas 203, 207may be associated with element user interface interactivity functions.The areas allow interaction from a user device (for example, via inputfrom a touchscreen, mouse click, etc.). The user interface interactivityfunctions may support a wide range of input, such as user text dataentry 701, 702, which may uniquely be linked to the respective elementarea 203, 207. According to the embodiment element areas 703 and 704could display different display colors to the user-device, and/or beassociated with multiple states for each specific element.

FIG. 7B illustrates an example of element area definition positionsaccording to an embodiment of the invention. According to theembodiment, the element area 207 may have a number of unique elementarea definition points 706, 707, 708, 709 whereby each elementdefinition point may have a unique x and y dimension co-ordinate value.The calculation of the values allows the creation of an interactiveelement area which may occupy this element area 207. The x and ydimension coordinates may then be used to calculate at least a portionof all the other previously referred dimensions: 401, 402 508, 510,which then allows the calculation of relative positional data for thiselement area 207 relative to the overall fixed-layout component area201.

FIG. 8A illustrates an example of the various data stores (database,metadata, files, etc.) associated with one or more fixed-layout areadisplay components, according to an embodiment of the invention.According to the embodiment, fixed-layout component 102, and with theoverall area 201, may be understood to be a background area of anoverall component relative to the element areas 202, 203, 204, 205, 206,207, 208 which may be visible in a foreground in a relative sense. FIG.8A further illustrates each fixed-layout component (at least a portionof background and foreground areas) may have associated graphics,digital images, multimedia, or other data associations 801. FIG. 8Afurther illustrates at least a portion of all the dimensional,positional, calculated, relative, layer data, file, and metadata 802 andelement user interactivities function association data 803 and otherdisplay, state, color and related associated data 804. At least aportion of this data and associated metadata and files and any derivedor further calculated data linking at least a portion of the data itemsto the overall fixed-layout component, including the elements, areassembled, and stored in the component package data store 805. Eachunique fixed-layout component may have its own associated data set whichmay be stored and managed on the overall component package data store804.

FIG. 8B illustrates an example of the various data stores (database,metadata, files, etc.) associated with one or more fixed-layout areadisplay components, according to an embodiment of the invention.According to the embodiment, fixed-layout component 102, and with theoverall area 201, (referring FIG. 2 ) may be understood to be abackground area of an overall component relative to the element areas202, 203, 204, 205, 206, 207, 208 which may be visible in a foregroundin a relative sense. FIG. 8B further illustrates each fixed-layoutcomponent (at least a portion of background and foreground areas) mayhave associated graphics, digital images, multimedia, or other dataassociations 801. FIG. 8B further illustrates at least a portion of allthe dimensional, positional, calculated, relative, layer data, file, andmetadata 802 and element user interactivities function association data803 and other display, state, color and related associated data 804, andassociated variable data rules and metadata data 807. FIG. 8Billustrates an example of the variable rules meta data store 807 whichassociates variable logic rule with found or derived element areas. Atleast a portion of this data and associated metadata and files and anyderived or further calculated data linking at least a portion of thedata items to the overall fixed-layout component, including theelements, are assembled, and stored in the component package data store805. Each element area, which can be either found/calculated or derivedelement areas (categories) can have variable data rule(s) associatedmetadata 807 which can support various display and data logic processingbased on user interactions. Each unique fixed-layout component may haveits own associated data set which may be stored and managed in theoverall component package data store 806.

FIG. 9 is a high-level flow diagram illustrating an exemplary processfor calculation of at least a portion of dimension data for items (e.g.element areas) which may be part of a fixed-layout component area,according to an embodiment of the invention. According to theembodiment, a fixed-layout component package preparation method isdepicted. Accordingly, a user device may initiate component packagedefinition process 901 by analyzing and preparing an overall componentarea and any associated graphics or digital image(s) for componentbackground area 201, analyze a plurality of defined areas assigned toeach associated element, and prepare any graphics or digital imagesassociated with the element(s) 902 as part of the overall component. Theprimary dimensions 301, 302, 401, 402, 503, 505 for the overall area andeach element(s) 202, 203, 204, 205, 206, 207, 208 are calculated in step903. At least a portion of the primary dimensions may be processedfurther 904 resulting in derived calculated dimensions to support therequirement that at least a portion of items in the overall fixed-layoutcomponent may support dynamically scaling and repositioning of theoverall component size and associated elements so that accuratepositional, size and display integrity is maintained. At least a portionof the display-layer data (referring, for example, to the system of FIG.2B) user interactivities types, different user states, and displaycolors, may be associated with each specific elements or overallcomponent area(s) as required in step 905. At least a portion of thedimension data (primary and calculated, derived) are then stored in thedimension's metadata data store 802. If elements have associated userinteractivities 905 this data may be assembled and stored in thecomponent package definition 803 data store. At least a portion of therelevant data items for the overall component may then be finallyassembled 906 from the various data sources 801 802 803 804 and may beplaced 907 in each component package data store 804. The method step 901may be repeated for at least a portion of components which require thedata definition.

Fixed Area Programmatic Display Window

FIG. 10A and FIG. 10B illustrate an example of a fixed area programmaticdisplay window which may be part of the overall user display window in adisplay screen, according to an embodiment of the invention. Accordingto the embodiment, a programmatically generated window area 1001, withpositional dimensions 1002 1004, and with area size dimensions 1003 and1005 may be shown. The position and size of this display window will becontrolled programmatically as part of an overall programmatic userinterface application on the user device. The fixed-layout component 102will be programmatically placed inside 106, 107, 108 the display window1001 and resized dynamically to fit within this actual display windowsize, while also maintaining the aspect ratio of fixed area component102, and at least a portion of the elements comprised within thefixed-layout package, and the relative size, position and display-layerdata of at least a portion of elements relative to each other as part ofthe overall component package. Further according to the embodiment,component 102 may be placed inside display window 1001 where the widthof the component may be dynamically resized to equal the width of thedisplay window 1001, and where there the depth of the component may beless than the display window resulting in an excess space area 1009.Further according to the embodiment, the aspect ratio of theprogrammatic display component 1001 may have the same aspect ratio asthe fixed-area component area 201, which would enable the fixed-areacomponent to exactly fit into the programmatic display window 1001.Display layer metadata may be used to ensure that at least a portion ofareas are shown to the user in the correct predefined sequence, andwhere some may overlap others ref FIG. 2B. The programmatic window 1001may be resized and repositioned dynamically in FIG. 10C the updatedwindow size and position 1010, driven by specific user interactivitieswith the overall programmatic application. The fixed-layout component102 will then dynamically resize to fit new window area 1010, while alsomaintaining the aspect ratio of the fixed area component 102, and theelements comprised therein, and that the relative size, position anddisplay-layer data of elements relative to each other may be maintainedas part of the overall fixed-layout component package.

FIG. 11 illustrates a plurality of exemplary fixed-layout windows and acomponent comprised therein as it is repositioned and automaticallyresized in various device screens display sizes, according to anembodiment of the invention. According to the embodiment, user interfacescreen 101, 1101, 1103, 1105, 1107 of a plurality of user devices aredepicted. Each user interface may comprise programming instructionsstored in the memory, the programming instructions, when executed by theprocessor may display the overall application to the user. Thefixed-layout content may display independently within the fixed areadisplay window provided 1109, 1102, 1104, 1106, 1108, as part of eachdevice display screen 101, 1101, 1103, 1105, 1107. The fixed-layout areamay be re-sized, re-scaled and repositioned independently anddynamically depending on end user requirements and the overallprogrammatic screen display logic.

FIG. 12 illustrates various examples of user devices 1201, 1202, 1203,and each comprising a programmatic display window 1204, 1205, 1206, andwhere the fixed-layout component may be automatically resized to fiteach provided programmatic display window, while maintaining at least aportion of positional, dimensional and aspect ratios within thefixed-layout component. According to the embodiment, the positioning offixed-layout content display 102 in one specific (same) device 1201,then repositioned in the same device 1202 in the same specificorientation and with different device orientation detailed in 1203. Asthe device orientation may be changed from portrait 1201 and 1202 tolandscape 1206 the fixed-layout component may be dynamicallyrepositioned and resized as a unified component within the overalldisplay area 102.

FIG. 13 details an example of a client device 1300 with an onlineapplication installed 1301 and communicating over a network 1306 with aserver application 1307. In this embodiment which details the exampleonline user interface module(s) 1302 which may reside on the clientdevice 1301. The online user interface module 1302 may be an integralpart of the user interface modules 1308, and which may be a component ofthe overall server system 1307.

The user client device(s) 1300 may communicate directly or indirectlywith the server 1307 and other systems 1312 via network(s) 1306. Deviceapplication 1301 user interface module 1302 may comprise programmaticcomponent 1303 and fixed-layout display UI component 1304. Online deviceuser-interface modules 1303, 1304 may be downloaded/synchronizedautomatically on use from the application server modules 1309, 1310.Programmatic client interface module 1303 may manage at least a portionof aspects of the user display and for programmatic generated contentand activities, and the creation, positioning, re-positioning andmanagement of the fixed area display window 1001 (referring to FIG.10A). Fixed-layout component module 1304 may manage aspects of thefixed-layout display components and any associated end-user generateddata 1313. This module may access the specific component package(s) forthe component(s) being displayed, it may then read the componentpackage(s) from the data store 804 and then process at least a portionof the comprised data, render and display the package(s) within one ormore fixed windows 1001 (referring to FIG. 10A) supplied by programmaticclient interface module 1304 and present that to the end user on thedevice screen. If associated user data exists this will then be accessedfrom the user data store 1313 and also presented to the user.

While the client device 1300 and online application server system 1307are presented with specific components, it should be understood by oneskilled in the art, that the architectural configuration of the system1300, 1307, 1312 may be simply one possible configuration and that otherconfigurations with more (or less) components are also possible toachieve the desired result.

FIG. 14 details an example of a client device 1401 with an installed ornative application (hereinafter referred to as “APP”) 1402, and whichcommunicates over networks 1410 with the server application 1307. Theuser client device(s) 1401 may communicate both directly and/orindirectly with the server 1307 and other systems 1312, 1408 via thenetwork(s) 1410. The original installation of the native application onthe device may be provided from application delivery server 1408. APP1402 installation module or program 1409 may provide the applicationinstallation files from data store 1410, and this data store may alsocomprise a version of component package data 804 for the fixed-layoutcomponent definitions. When the initial installation has completed acopy of the component package data 804 may then also reside with orinside APP 1402 on actual user device 1401. Component package APP datastore 804 inside APP 1402 may also receive subsequent automatic orad-hoc updates from a different or updated version of this data filewhich may be stored on the online application server system 1307 or theapplication delivery server 1408.

Installed APP 1402 and online client software 1301 may both existseparately and may be independent of each other on any specific samedevice 1300, 1401. APP 1402 user interface module may comprise its ownprogrammatic component module 1404 and fixed-layout component module1405. APP 1402 programmatic client interface module 1404 may manageaspects of the user display and for programmatic generated content andinteractivities and the creation, positioning, re-positioning andmanagement of fixed area display window 1001 (referring to FIG. 10A).The fixed component module 1405 may manage aspects of the fixed-layoutdisplay components and any associated end-user generated and or userderived data 1407. This fixed-layout component module 1405 may access aspecific version of the component package 804 inside or directlyassociated with APP 1402 for the component being displayed (within APP1402). Fixed-layout module 1405 may then read the component package fromdata store 804 and then process at least a portion of the compriseddata, render, and display the fixed-layout package within the fixeddisplay window 1001 supplied by programmatic client interface module1404 and display that to the end user device. If user data 1407 whichmay be associated with APP 1402, the fixed-layout component module willalso then retrieve and display data 1407 for the user via fixed-layoutmodule 1405.

The user may interact with the fixed element areas 202, 203, 204, 205,206, 207, 208 as part of specific component 201. Fixed element areas areconfigured to receive user-entered data 701 and 702, whereby this datamay be saved to APP data store 1407 via the application logic modules1406. If the user element data is already in data store 1407 (within theAPP 1402, for example, from a previous save) it may bedisplayed/redisplayed to the associated user interface on completion anddisplay of the fixed-layout component. Application (APP) user data store1407 may update (as required) online application server system 1307 userdata store 1313 via the server application programming interface (API)module 1311.

While client device 1300, 1401 and server systems 1307, 1408, arepresented with specific components, it should be understood by oneskilled in the art, that the architectural configuration of the system1401, 1408, 1307 may be simply one possible configuration and that otherconfigurations with more (or less) components are also possible toachieve the desired result.

FIG. 15 is a high-level flow diagram illustrating an exemplary processfor programmatically loading and displaying a plurality of fixed-layoutcomponents, according to an embodiment of the invention. According tothe embodiment, user device software (online 1301, or native/installedapp 1402) software load and display process 1500: In some embodiments,the device display software 1302, 1403 may load programmatic module1303, 1404 and may then complete initial initialization 1501 for a userdevice display. If a user device display comprises fixed-layoutcomponent 1502, programmatic device interface module 1303, 1404 mayinitialize 1503 viewing display window 1001 for the fixed-layoutcomponent. Fixed-layout component device interface module 1304, 1405 maythen access the specific component 1504 from the component data store804, where at least a portion of the data may then be processed 1505 andthe fully assembled/rendered fixed-layout package comprising at least aportion of its associated items may be then presented to the displaywindow 1001 in step 1506, while dynamically resizing as required. Ifend-user data 1313, 1407 exists and is associated with the specificfixed-layout component being displayed, this data may be retrieved anddisplayed 1507 to the user by the modules 1304, 1405. Device softwareload and display process 1500 may be repeated from step 1502 for atleast a portion of fixed-layout components which may be part of thedevice screen (referring to FIG. 1B).

FIG. 16A and FIG. 16B illustrate an exemplary embodiment of afixed-layout component combined with programmatic display elements on ascreen of a user device with a plurality of orientations, according toan embodiment of the invention. According to the embodiment, support formultiple orientations of landscape 1601 and portrait 1606 may be shown.The user device 1601, 1606, details the display 1602, 1607, wherebyprogrammatic display area 1603, 1610 may be shown, and in contrast thefixed-layout area 1604, 1608 may be also shown. Further according to theembodiment programmatic text 1603, 1610 and fixed-layout component 1604may be displayed. Programmatic text 1603 may be user selectable, whereasfixed component text 1604, 1608 may be non-selectable and may becomprised, for example, on the fixed-layout area background digitalgraphic, and where the scaling may determine the text size of thefixed-layout component package within the window 1001 (referring to FIG.10 ). An example of a user interactivity element is detailed in 1605,1609, whereby its position and function are managed by the fixedcomponent modules 1304, 1405 and may be independent of the overallprogrammatic application modules 1303, 1404. Display window 1001 sizeand position may be different across the device orientations 1601 and1606 which may result in different size scaling of the fixed-layoutcomponent.

FIG. 16C illustrate another exemplary embodiment of a fixed-layoutcomponent combined with programmatic display elements on a mobile devicewith interactive variable components, according to an embodiment of theinvention. According to the embodiment, support for multipleorientations of landscape 1601 and portrait 1606 are shown.

Mobile computing device 1601 comprises display 1602 whereby programmaticdisplay area 1603 may be shown, and, in contrast, fixed-layout area 1604may also be shown. Further according to the embodiment programmatic text1603 and fixed-layout component 1604 may be displayed. Programmatic text1603 may be user selectable, whereas fixed component text 1604 may, insome embodiments, be non-selectable and may be comprised, for example,on the fixed-layout area background digital graphic, and where thescaling may determine a text size of the fixed-layout component packagewithin the window 1001 (referring to FIG. 10A-10B). In some embodiments,areas 1610 and 1615 comprise areas where interactivity, for example viaI/O 48 (referring to FIG. 23 ) whereby position and function are managedby the fixed component modules 1304 (referring to FIG. 13 ) and 1405(referring to FIG. 14 ) and may be independent of the overallprogrammatic application modules 1303, 1404. Display window 1001 sizeand position may be different across the device orientations 1601 and1606 which may result in different size scaling of the fixed-layoutcomponent. The user interactivity element area 1610 comprises foundelement area 1611 whereby it may display dynamic variable data 1612in/on this found element area 1611. User interactivity element 1610,operable to receive data via, for example, via I/O 48 may comprisevariable data 1612 and be logically associated with one or more variablelabels 1613 which may, in some embodiments, be comprised on thebackground fixed-layout area 1604.

FIG. 18A illustrates an exemplary embodiment of a fixed-layout contentcomponent item 102 that comprises element areas 1801, 18021, 18031,18041, 1813, 1815, 1817 that may be comprised in/on fixed-layout contentitem 201, and that may form a basis for new element items 1824, 1808,1809, 1810, 1814, 1816, 1818 (for example, as defined in FIG. 2A: 202,203, 204, 205, 206, 207, 208). Element area items 1825, 1808, 1809,1810, 1814, 1816, 1818 may be automatically derived from highlightedareas 1801, 18021, 18031, 18041, 1813, 1815, 1817. Newly derived andcalculated element areas 1825, 1808, 1809, 1810, 1814, 1816, 1818, areoperable to support additional interactivity via I/O devices 48.

FIG. 18A further illustrates an exemplary fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 1801, 18021, 18031, 18041, 1813, 1815, 1817, that may be in aforeground on a relative basis (in some embodiments this may be seen asa layer). Further according to the embodiment, fixed-layout component102 may comprise fixed-layout content item area 208, any number ofdigital graphics (for example, to makeup a full or partial area 208),items such as text, pictures, shapes, and a plurality of highlightedoutline areas 1801, 18021, 18031, 18041, 1813, 1815, 1817 may beembedded as part of content item area 208. An overall objective, in apreferred embodiment, may be to automatically find and create elementitem areas (as defined in FIG. 2A: 202-208) which may be based on thehighlighted exemplary areas 1801, 18021, 18031, 18041, 1813, 1815, 1817.Further according to the embodiment, new element item areas 1825, 1808,1809, 1810, 1814, 1816, 1818, may be dimensionally sized andpositionally located such that the element item areas may reside justwithin exemplary highlighted areas 1801, 18021, 18031, 18041, 1813,1815, 1817. An objective is therefore to automatically identify aplurality of areas (that is, a plurality of automatically found andcalculated element areas) which may be inside each of areas 1801, 18021,18031, 18041, 1813, 1815, 1817. The automatically found element areaitems comprising dimensional, positional, and display-layer data maythen be each added as new element area items to fixed-layout packagedata stores 806 (referring to FIG. 8A).

Further according to the embodiment, a process is disclosed that mayautomatically find and calculate element item areas 1825, 1808, 1809,1810, 1814, 1816, 1818, which are the dashed line figure area inside thehighlighted area 1801, 1802, 1803, 1804, 1813, 1815, 1817, asillustrated. It should be noted that the automatically found elementitem areas illustrated 1824, 1808, 1809, 1810, 1814, 1816, 1818, (dashedline figure) may be marginally smaller than the highlighted area 1801,1802, 1803, 1804, 1813, 1815, 1817 identified as part of the backgroundimage.

In other embodiments an automatically found and calculated areas be mayequal to or greater than (or much less than) highlighted areas 1825,1808, 1809, 1810, 1814, 1816, 1818. automatically found elementdefinition points 706, 707, 708, 709 coordinates may then be used tofurther derive definition data (referring to FIG. 8A) required in the802 dimension and positional data store which may then support a finalassembly of fixed-layout component definition data 806. There may bemany other alternative methods to determine element definition points706, 707, 708, 709 coordinates to calculate width 401, height 402, andposition of at least a portion of element areas relative (as in FIG. 5A:508, 510) to the overall fixed-layout content item. Automaticallycalculated element item areas 1824, 1808, 1809, 1810, 1814, 1816, 1818(dashed line figure) may be pre-defined as a percentage smaller than theboundary of the highlighted area 1801, or it may be a same size or alsolarger, depending on the requirement or configuration.

FIG. 18B illustrates an embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areasembedded as part of any number of digital graphics, and computations ofone or more derived areas, according to an embodiment of the invention.According to the embodiment, fixed-layout content component item 102comprises element area 1801 that may be comprised in/on fixed-layoutcontent item 201, and that may form a basis for new automatically foundelement area items 18316 (for example, as defined in FIG. 2A: 202,203,204, 205, 206, 207, 208), and also new derived element area 18317.Derived element area items 18317 may be derived (that is, calculated)automatically from the automatically found areas 18316 and which in turnis derived from the highlighted element areas 1801. Newly derivedelement area 18317 or the automatically found and calculated elementareas 18316 may be configured to support additional user interaction701, 702 (referring to FIG. 7A).

FIG. 18B further illustrates an exemplary fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 1801 that may be in a foreground on a relative basis (in someembodiments this may be seen as a layer). Further according to theembodiment, fixed-layout component 102 may comprise fixed-layout contentitem area 208, any number of digital graphics (for example, to makeupthe full or partial area 208), items such as text, pictures, shapes, andthe highlighted element outline areas 1801 may be embedded as part ofcontent item area 208.

An overall objective, in a preferred embodiment, may be to automaticallyfind and create element item areas (as defined in FIG. 2A, for example202-208) which may be based on the highlighted exemplary element area.Further according to the embodiment, new automatically found elementitem areas 18316, may be dimensionally sized and positionally locatedsuch that the element item areas may reside at the exemplary highlightedelement area 1801. Further according to the embodiment, the data whichwas used to automatically find and calculate the found element area18316, may then be processed further to enable the creation of anadditional new derived element area 18317. In a preferred embodimentthis further derived area processing may be based on a percentage orpixel dimension adjustments (or combinations) to the found andcalculated element area 18316 overall dimensions and any relativepositioning of the derived area 18317 relative to the found area 18316.

Component area 201 may have associated dimension x-Axes 18303 and y-Axes18302 and direction (referring to FIG. 5A and FIG. 5B). Accordingly,each fixed-layout element may have an associated reference point in atwo-dimensional dimension display grid which may have an x-Axis 502 anda y-Axis 503 (referring to FIG. 5A and FIG. 5B). Each Axes may each havedimensional values from 0 (18301), 1 to “n” (18303) as for the x-Axisand from 0 (18302), 1 to “n” (18302) as shown for the y-Axis. Eachdimension point will have an x and y dimension pair value in the x-ytwo-dimensional dimension grid. Further according to the embodiment,element area 208 may have associated reference point 18301 displayedwhich may have a unique x and y co-ordinate pair values for dimensionposition. In this embodiment, the component reference point 18301 mayhave a position of 0, 0 for the x-y dimension's pair.

Any position (represented by a x-y location pair) in the fixed elementarea 208 may have additional dimension adjustments applied to enable thecalculation of an additional derived location represented by its ownunique x-y location pair. Referring to the X Axis 18303 and Y Axisdirections 18302 which are classified as positive X and Y directionsrespectively whereas 18321 and 1832 are classified as negative X and Ydimension directions respectively in this embodiment. In thisembodiment, position 18312 may be derived from position 706, position18313 may be derived from position 707, position 18314 may be derivedfrom position 708, and position 18315 may be derived from position 709in this preferred embodiment. Accordingly beginning with position 706and adding a positive X and Y dimension adjustments to derive thelocation position 18312, and conversely, beginning with position 18312and adding a negative X and Y dimension adjustments to derive thelocation position 706 according to this embodiment. So, position 707would have a negative X and positive Y dimension adjustments applied toderive the location position 18313, and conversely position 18313 wouldhave positive X and negative Y dimension adjustments applied to derivethe location position 707 according to this embodiment. Accordingly,position 708 would have a negative X and positive Y dimensionadjustments applied to derive the location position 18314, andconversely position 18314 would have positive X and negative Y dimensionadjustments applied to derive the location position 708 according tothis embodiment. So, position 709 would have a positive X and positive Ydimension adjustments applied to derive the location position 18315, andconversely position 18315 would have negative X and negative Y dimensionadjustments applied to derive the location position 709 according tothis embodiment.

The positive and negative direction dimension adjustments for both the Xany Y direction are referred to as: ΔX_(positive) 18304, ΔX_(negative)18305, ΔY_(positive) 18306, ΔY_(negative) 18307 according to theembodiment. In an embodiment, these dimension and positional adjustmentsin the X any Y directions may be defined in terms of an absolute numberof pixels for each of the defined search directions. Each searchdirection can have different number of pixels adjustments applied. Inanother embodiment, these positive or negative dimension adjustments mayalso be defined as a percentage of element width 401 or height 402(referring to FIG. 4 ). Each search direction may have a differentpercentage adjustments applied. In another embodiment, these positive ornegative dimension adjustments may be defined as a percentage of aspecified element area (referring 202, FIG. 2A) resulting in acalculated a number of pixels, and where these “calculated number ofpixels” are then applied as adjustments to some or all of the otherelement areas (referring 203, 204, 205, 206, 207, FIG. 2A). In anotherembodiment these positive or negative dimension adjustments may also bedefined in terms of a combination of absolute number of pixels or adefined percentage for each of the directions X and Y, i.e. eachspecific search direction can be either a number of pixels or percentagecalculation.

Direction 18304 is ΔX_(positive) which may be a positive number,direction 18305 is ΔX_(negative) which may be a negative number,direction 18306 is ΔY_(positive) which may be a positive number,direction 18307 is ΔY_(negative) which may be a negative number.

In the illustrated FIG. 18B embodiment, ΔX₁ 18318 is a ΔX_(positive) andis a positive number, ΔX₂ 18319 is a ΔX_(negative) and is a negativenumber, ΔY₁ 18321 and ΔY₂ 18319 are both ΔY_(positive) and therefore arepositive numbers.

In the FIG. 18B the general notation X_(ea), Y_(ea) refers to theposition of the element area i.e. “ea”. The notation X_(fc), Y_(fc)refers to the position of the found and calculated element area. i.e.“fc”. The notation X_(d), Y_(d) refers to the position of the derivedelement area. i.e. “d”.

In the FIG. 18B embodiment, the x-y coordinates for the derived position18312 X_(d1), Y_(d1) may be calculated from position 706 X_(fc1),Y_(fc1) as follows: X_(d1)=X_(fc1)+ΔX₁, Y_(d1), =Y_(fc1)+ΔY₁. The x-ycoordinates for the derived position 18313 X_(d2), Y_(d2) may becalculated from position 707 X_(fc2), Y_(fc2) as follows: X_(d2),=X_(fc2)+ΔX₂, Y_(d2), =Y_(fc2)+ΔY₂. The x-y coordinates for the derivedposition 18314 X_(d3), Y_(d3) may be calculated from position 708X_(fc3), Y_(fc3) as follows: X_(d3), =X_(fc1)+ΔX₂, Y_(d3), =Y_(fc3)+ΔY₂.The x-y coordinates for the derived position 18315 X_(d4), Y_(d4), maybe calculated from position 709 X_(fc1), Y_(fc1) as follows: X_(d4),=X_(fc4)+ΔX₁, Y_(d4), =Y_(fc4)+ΔY₁. Referring to FIG. 18A, the derivedarea 1832 with width 1851 and height 1853 may be calculated, and all thex, y derived coordinates and associated derived metadata may be storedin the element area metadata data stores 804, 805 and 806 (referring toFIG. 8B).

In other embodiments the dimensions for ΔX₁, ΔX₂ ΔY₁, ΔY₂ can bepositive or negative for each or some or all of these values, therebyallowing the calculation of derived areas 18317 which can be positionedat any location relative to the originally found and calculated area18316.

FIG. 18C illustrates another exemplary embodiment of a fixed-layoutcomponent comprising the fixed-layout content background area, one ormore digital graphics, visual items that may comprise one or morehighlighted areas embedded as part of any number of digital graphics,and computations of one or more derived areas, according to anembodiment of the invention. According to the embodiment, fixed-layoutcontent component item 102 comprises element areas 1801, 1830 that maybe comprised in/on fixed-layout content item 201, and that may form abasis for new automatically found (referring to FIG. 26A) element areaitems 1831, 1849 (for example, as defined in FIG. 2A: 202, 203, 204,205, 206, 207, 208), and also new derived element areas 1832, 1850.Derived element area items 1832 and 1850 may be derived (that is,calculated) automatically (referring to FIG. 26B) from the automaticallyfound areas 1831 and 1849 and which are in turn derived from thehighlighted areas 1801, 1830. Newly derived element areas 1832, 1850 orthe automatically found and calculated element areas 1832, 1949, mayboth be configured to support additional user interaction 702 (referringto FIG. 7A).

FIG. 18C further illustrates an exemplary fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 1801, 1830, that may be in a foreground on a relative basis (insome embodiments this may be seen as a layer). Further according to theembodiment, fixed-layout component 102 may comprise fixed-layout contentitem area 208, any number of digital graphics (for example, to makeupthe full or partial area 208), items such as text, pictures, shapes, andtwo highlighted outline areas 1801, 1830 may be embedded as part ofcontent item area 208.

An overall objective, in a preferred embodiment, may be to automaticallyfind and create element item areas (as defined in FIG. 2A: 202-208,etc.) which may be based on the highlighted exemplary areas 1801, 1830.Further according to the embodiment, new automatically found elementitem areas 1831, 1849, may be dimensionally sized and positionallylocated such that the element item areas may reside at exemplaryhighlighted areas 1801, 1830. Further according to the embodiment, thedata which was used to automatically find and calculate the foundelement areas 1831, 1849 may then be processed further to enable thecreation of additional new derived element areas 1832, 1850. In apreferred embodiment this further derived area processing may be basedon a percentage or pixel (or combinations thereof) dimension adjustmentsto the found element area 1831 overall dimensions and relativepositioning of the derived area 1832 relative to the found area 1831.

The derived area 1850 is based on the found area 1849 which is based onthe element area 1801. The derived area 1832 is based on the found area1831 which is based on the element area 1830. For the highlighted area1830, the automatically found element area 1832 supports area dimensions1852 and 1854, whereas the automatically derived element area supportsdimensions 1851 and 1853.

Each search direction 1803, 1807, 1804, 1806 may have a positive ornegative (increase or decrease) percentage or pixel dimension 1846,1835, 1840, 1843 and position adjustments applied to each searchdirection which then enables the calculations for positions 1836, 1837,1844, 1845 to be mathematically derived from the positions at 1834,1839, 1842, and 1847. Each search direction 1803, 1807, 1804, and 1806may have its own percentage or pixel dimension 1836, 1840, 1843, 1846parameters applied and as either an increase 1856 or decrease 1855 inrelation to the automatically found element area 1831, and 1849.

In another embodiment the found element areas 1849 may have thedimension adjustments 1846 1835 1840 1843 applied after the automaticsearching has concluded (in search directions 1803, 1804, 1806, 1807)and to then automatically generate the new derived element areas 1850.

An objective is therefore to automatically identify a plurality of areas(that is, a plurality of automatically found and calculated elementareas) which may be inside each of areas 1831, 1849, and also thenautomatically generate derived element areas based on the application ofeither positive or negative percentage or pixels dimensions applied toeach element area border. The automatically found and derived elementarea items comprising dimensional, positional, and display-layer datamay then be each added as new element area items to fixed-layout packagedata stores 806 (referring to FIG. 8A).

FIG. 18D illustrates another exemplary embodiment of a fixed-layoutcomponent comprising the fixed-layout content background area, one ormore digital graphics, visual items that may comprise one or morehighlighted areas embedded as part of any number of digital graphics,and where derived areas examples are shown, according to an embodimentof the invention. According to the embodiment, an exemplary fixed-layoutcontent item 208 may be defined as a background area 208 relative to anyelement areas 1801, 1830, whereby element areas 1801 and 1830 may be ina foreground on a relative basis (in some embodiments this may be seenas a layer). Further according to the embodiment, fixed-layout component102 may comprise fixed-layout content item area 208, any number ofdigital graphics (for example, to makeup the full or partial area 208),items such as text, pictures, shapes, and the highlighted element areas1860, 1862, 1864, 1866, 1868, 1870, 1872, 1874, 1874, 1878 may beembedded as part of content item area 208. An overall objective, in apreferred embodiment, may be to automatically find and create thederived element item areas (as defined in FIG. 18C: 1832, 1850) for atleast a portion of the outline's areas 1860, 1862, 1864, 1866, 1868,1870, 1872, 1874, 1874, 1878 and which results in the calculation of thederived element areas 1861, 1863, 1865, 1867, 1869, 1871, 1873, 1875,1877, 1879. As defined in FIG. 18C, each derived element area 1832, 1850is calculated from each automatically found element area by applying apositive or negative percentage or pixels dimensions adjustment 1855,1856 for each search direction. The automatically found and derivedelement area items comprising dimensional, positional, and display-layerdata may then be each added as new element area items to fixed-layoutpackage data stores 806 (referring to FIG. 8A).

FIG. 18E illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, and where derived areas are found and shown according tovarious embodiments of the invention. According to the embodiment,fixed-layout content item 208 that may be defined as a background area208 relative to any element areas 1801, 1830, that may be in aforeground on a relative basis (in some embodiments this may be seen asa layer). Further according to the embodiment, fixed-layout component102 may comprise fixed-layout content item area 208, any number ofdigital graphics (for example, to makeup the full or partial area 208),items such as text, pictures, shapes, and two highlighted outline areas1801, 1830 may be embedded as part of content item area 208. An overallobjective, in a preferred embodiment, may be to automatically find andcreate element item areas (as defined in FIG. 2A: 202-208) which may bebased on the highlighted exemplary areas 1801, 1830. Further accordingto the embodiment, new automatically found element item areas 1831,1849, may be dimensionally sized and positionally located such that theelement item areas may reside at exemplary highlighted areas 1801, 1830.Further according to the embodiment, the highlighted outline area 1801is bordered on three sides 1848, 1833, 1838, by lines, whereas thefourth side 1890 is bounded by some text and or graphic on/in thebackground area 208. The search direction 1806 will stop at position1845, resulting in the automatically found element area 1849. Theautomatically found element area 1849 then enables a derived elementarea 1850 to be calculated (as defined referring to FIG. 18C). Theautomatically found and derived element area items comprisingdimensional, positional, and display-layer data may then be each addedas new element area items to fixed-layout package data stores 806(referring to FIG. 8A).

FIG. 18F illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, and where derived areas are found and shown according tovarious embodiments of the invention. According to the embodiment,fixed-layout content item 208 that may be defined as a background area208 relative to any element areas 18101, 18106, 18111, 18116, that maybe in a foreground on a relative basis (in some embodiments this may beseen as a layer). Further according to the embodiment, fixed-layoutcomponent 102 may comprise fixed-layout content item area 208, anynumber of digital graphics (for example, to makeup the full or partialarea 208), items such as text, pictures, shapes, and four highlightedoutline areas 18101, 18105, 18106, 18107, 18111, 18112, 18116, 18117,18121, 18122 may be embedded as part of content item area 208. Anoverall objective, in a preferred embodiment, may be to automaticallyfind and create found element item areas 18102, 18108, 18113, 18118 (asdefined in FIG. 2A: 202-208, etc.) from a start position 18104, 18109,18115, 18120 and which may be based on the highlighted exemplary areas18101, 18106, 18111, 18116. Further according to the embodiment, theautomatically found areas 18102, 18108 18113, 18118 utilized certainsample text or graphic 18105, 18107, 18112, 18117, 18121, 18122 as oneor more boundaries to the automatically found element areas.Automatically found 18102, 18108, 18112, 18118 and derived (referring toFIG. 18C) element area items 18103, 18110, 18114, 18119 comprisingdimensional, positional, and display-layer data may then be each addedas new element area items to fixed-layout package data stores 806(referring to FIG. 8A).

FIG. 18G illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, and where derived areas are found and shown according tovarious embodiments of the invention. According to the embodiment,fixed-layout content item 208 that may be defined as a background area208 relative to any element areas 1831, 1836, 18140, 18144, that may bein a foreground on a relative basis (in some embodiments this may beseen as a layer). Further according to the embodiment, fixed-layoutcomponent 102 may comprise fixed-layout content item area 208, anynumber of digital graphics (for example, to makeup the full or partialarea 208), items such as text, pictures, shapes, a plurality ofhighlighted outline areas 18131, 18136, 18140, 18144, and text/graphics18135, 18137, 18141, 18145, 18147 may be embedded as part of contentitem area 208. An overall objective, in a preferred embodiment, may beto automatically find and create element item areas 18132, 18138, 18143,18148 (as defined in FIG. 2A: 202-208) from a search start position18134, 18139, 18142, 18146. Further according to the embodiment, theautomatically found element areas 18133, 18138, 18143, 18148 utilizedcertain sample text or graphic 18135, 18137, 18141, 18145, 18147 as oneor more boundaries to the automatically found element areas.Automatically found and calculated and derived (referring to FIG. 18A)element areas 18132, 18133, 18138, 18143, 18148 items comprisingdimensional, positional, and display-layer data may then be each addedas new element area items to fixed-layout package data stores 806(referring to FIG. 8A).

FIG. 18H illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, and where a found element area is spread across differentareas in the background area, according to an embodiment of theinvention. According to the embodiment, fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 1801 that may be in a foreground on a relative basis (in someembodiments this may be seen as a layer). Further according to theembodiment, fixed-layout component 102 may comprise fixed-layout contentitem area 208, any number of digital graphics (for example, to makeupthe full or partial area 208), items such as text, pictures, shapes, andtwo highlighted outline areas 1801 may be embedded as part of the fixedarea 208. An overall objective, in a preferred embodiment, may be toautomatically find and create element item area (as defined in FIG. 2A:202-208) where the background fixed layout area 201 comprises differentareas 18160, 18162, 18163, 18170 and which may comprise differentdigital graphics and/or including different pixel color properties, andwhere the search logic and associated setting to be used arespecifically defined in detail.

According to the embodiment, advanced search logic may relate to thedefined search directions and additional associated search configurationsettings for each search direction to enable the finding of more complexautomatically found element area 1801. Referring now to FIG. 18H thebackground area 208 comprises additional internal areas 18160, 18162,18163, 18170 in addition to an element area outline 1801. Internal areas18160, 18162, 18163, 18170 may comprise different graphics and or pixelcolor (s).

It may be observed that if an automatic simple (first change of pixelcolor in any direction) search commences at location 1805 (and where thebackground of 18162 has different coloring to areas 18160 and 18163)this would result in an automatic element area being found and this areawould have positional coordinates 18071, 18172, 18173, 18174.

In an embodiment, enhanced search logic may be defined such that theautomatically found element area 1849 may be found (at the element area1801) and where this element area 1801 and found element area 1849 spansacross multiple areas 18162, 18163, 18170 and whereby each may havedifferent pixel color properties. In this embodiment the enhanced searchlogic is defined such that for the search direction 1803, that thesearch in that direction stops after the first pixel color change atlocation 18168, and co-ordinates X_(nf6), Y_(nf6), (where “nf”=nextfound co-ordinates reference) and for search direction 1804, that thesearch in that direction stops at the third pixel color change atlocation 18167 X_(nf3), Y_(nf3), and for search direction 1806, that thesearch in that direction stops at the first pixel color change 18169,X_(nf7), Y_(nf7), and for search direction 1807, that the search in thatdirection stops at the second pixel color change at location X_(nf5),Y_(nf5). In search direction 1804 the first pixel color change islocated at 18166 X_(nf1), Y_(nf1), the second at 18175 X_(nf2), Y_(nf2),and the third at 18167 X_(nf3), Y_(nf3). In search direction 1807 thefirst pixel color change is located at 18165 X_(nf4), Y_(nf4), and thesecond at 18174 X_(nf5), Y_(nf5).

In an embodiment an enhanced search logic is configured such that: thesearching in direction 1804 will stop after reaching three pixel colorchanges, the search direction 1806 will stop after one pixel colorchange, the search direction 1807 will stop after two pixel colorchanges, and search direction 1803 will stop after one pixel colorchange.

In an embodiment the automatic and enhanced search logic configurationfor element area 1801 commences by defining or selecting a pre-definedSearch Logic to apply before the search start 1805. In this embodimentthe overall enhanced search logic is configured such that each searchdirection 1803, 1804, 1806, 1807 may be individually configured suchthat the search stops in each direction after the specified number ofchanges in pixel color is reached. In FIG. 18H, the searching in thesearch direction 1807 may be configured to stop after reaching a secondpixel color change. The search commences the search from 1805 and fordirection 1807, and continues to location 18165 where it detects andrecords the first pixel color change, and then the search 1807 continuesto location 18164 where the search records the second pixel color changeand where the search then stops as it has completed its pre-definedsearch logic criteria of finding and stopping the search at the secondpixel color change. The search in direction 1804 is also pre-configuredin the enhanced search logic before starting such that the search willstop on finding the third change of pixel color values/properties. Thesearch commences 1805 and progresses in direction 1804, and continues tolocation 18166 where it detects and records the first pixel colorchange, and then the search 1804 continues to location 18175 where thesearch records the second pixel color change, and where the searchcontinues to the third pixel change 18167 and where the search thenstops as it has completed its pre-defined criteria of finding andstopping the search at the third pixel color change. In someembodiments, the search direction 1803 may be pre-configured beforestarting such that the search may stop on finding the first change ofpixel color values/properties. The search commences 1805 and progressesin direction 1803, and continues to location 18168 where it may detectand record a first pixel color change, and where the search then stopsas it has completed its pre-defined criteria of finding and stopping thesearch at the first pixel color change. The search 1806 commences andprogresses in direction 1803 and continues to location 18168 where itdetects and records the first pixel color change; and where the searchthen stops as it has completed its pre-defined criteria of finding andstopping the search at the first pixel color change. Each searchdirection 1803, 1804, 1806, 1807 may be configured with its own searchparameters to determine when the searching stops and based on the pixelcolor change.

FIG. 18I illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, whereby the highlighted areas comprise at least one bordercoinciding with an edge of the fixed-layout component, according to anembodiment of the invention. According to the embodiment, fixed-layoutcontent component item 102 that comprises element areas 18201, 18210that may be comprised in/on fixed-layout content item 201, and that mayform a basis for new automatically found element area items 1849, 18209(for example, as defined in FIG. 2A: 202, 203,204, 205, 206, 207, 208).

FIG. 18I further illustrates an exemplary fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 18201, with borders 18202, 18203, 18204 and the border edge 18205of being part of the edge of the overall background area 201 and forarea 18210, and with borders 18206, 18208, 18209, 18207 for area 18210.The highlighted area 18201, 18210 may be in a foreground on a relativebasis (in some embodiments this may be seen as a layer). Furtheraccording to the embodiment, fixed-layout component 102 may comprisefixed-layout content item area 208, any number of digital graphics (forexample, to makeup the full or partial area 208), items such as text,pictures, shapes, and a plurality of illustrated element areas 18201,18210 may be embedded as part of content item area 208. For element area18202 the search may commence from start 1805 for at least a portion ofthe defined directions. The search direction 1807 may conclude when nopixel change has been recorded but where the edge of the background area201 has been reached 18164 and this location is then recorded as theconclusion to this 1807 search direction. The search in at least aportion of the other directions 1803, 1804, 1806 may also concluded. Theautomatically found element area item 1849 comprising dimensional,positional, and display-layer data may then be each added as new elementarea items to fixed-layout package data stores 806 (referring to FIG.8A).

For element area 18210 this is constructed with one border 18220 insidethe fixed area component 208 and the border for the remaining threesides 18206 18207 18209 are the border edges of the fixed area componentarea 18210. The search commences from any position 18217 inside the area18210 and for at least a portion of the defined directions. The searchfor boundaries 18215, 18216, 18219 each concludes when no pixel changehas been recorded but where the edge of the background area 201 has beenreached and the dimensions data are then recorded as the conclusion tothe search directions. The search in at least a portion of the finaldirection 18218 may also concluded. The automatically found element areaitem 18210 comprising dimensional, positional, and display-layer datamay then be each added as new element area items to fixed-layout packagedata stores 806 (referring to FIG. 8A).

FIG. 18J illustrates an exemplary embodiment of a fixed-layout componentcomprising the fixed-layout content background area, one or more digitalgraphics, visual items that may comprise one or more highlighted areaswith different borders embedded as part of the one or more digitalgraphics, further comprising different derived area calculations wherebyone or more border edges are shown, further comprising differentsettings for calculated derived areas, according to an embodiment of theinvention. According to the embodiment, fixed-layout content item 208that may be defined as a background area 208 relative to any elementareas 1801, 1817, 1815, 1813, 1802, 1803, 1804, 1852, 1853, 1856, thatmay be in a foreground on a relative basis (in some embodiments this maybe seen as a layer). Further according to the embodiment, fixed-layoutcomponent 102 may comprise fixed-layout content item area 208, anynumber of digital graphics (for example, to makeup the full or partialarea 208), items such as text, pictures, shapes, and highlighted outlineareas 1801 1817 1815, 1813, 1802, 1803, 1804, 1852, 1853, 1856, may beembedded as part of content item area 208.

An objective of the enhanced search logic, in a preferred embodiment,may be to automatically find one or more adjacent found element areas1808, 1809, 1861 and which may have the same calculations applied togenerate associated derived element areas 1858, 1859, 1860. The searchlogic may be defined to start in any location 1812, direction 1811,inside area 1802, and to specifically find a plurality (for example,three) adjacent areas, and at least a portion of which will then havethe same derived calculation settings applied to create the derivedareas 1858, 1859, 1860. The derived element area calculation settingsmay be defined before a selection of search start 1812.

Another overall objective, in another preferred embodiment for searchconfiguration, may be to automatically find a certain specified numberof adjacent found element areas 1850, 1855, 181857 (to the end of alist) that may have the same calculations applied to generate associatedderived element areas 1851, 1854, 1862. The search logic is configuredsuch that search may be defined to start 1863 in direction 1864 andconclude when at least a portion of remaining adjacent element areas arefound 1850, 1855, 1857. The derived element areas 1851, 1854, 1862 maythen be calculated. The derived element area settings defined before thesearch start 1863 may be different to the derived element area settingsdefined before the search start 1812.

An objective for searches 1811, 1864 may be to automatically identify aplurality of areas 1808, 1809, 1861, 1850, 1855, 1857 (that is, aplurality of automatically found and calculated and element areas) andto automatically calculate a plurality of derived element areas 1858,1859, 1860, 1851, 1854, 1862, and in addition, the derived element areasmay have different calculations applied such that areas 1858, 1859, 1860may be different dimensionally and positionally compared to areas 1851,1854, 1862, even though the source element areas 1802, 1803, 1804, 1852,1855, 1856 may have similar dimensional layouts. The automatically foundand automatically derived element area items comprising dimensional,positional, and display-layer data may then be added as new element areaitems to fixed-layout package data stores 806 (referring to FIG. 8A).

FIG. 18K illustrates an exemplary embodiment of a fixed-layout component102 comprising the fixed-layout content background area 201, one or moredigital graphics, visual items that may comprise one or more highlightedareas with different borders embedded as part of the one or more digitalgraphics, further comprising variable label items on the backgroundarea, (18101, 18104, 18106, 18107, 18122, 18125), and with linkedvariable data items displayed (18116, 18109) within the displayproperties of found or derived areas (18102, 18103, 18108, 18110, 18124,18126) in a layer on (or in front of) the background area according toan embodiment of the invention. According to the embodiment,fixed-layout content item 208 that may be defined as a background arearelative to any element areas 18101, 18106, 18122, that may be in aforeground area on a relative basis (in some embodiments this may beseen as a layer). Further according to the embodiment, fixed-layoutcomponent 102 may comprise fixed-layout content item area 208, anynumber of digital graphics (for example, to makeup the full or partialarea 208), items such as text, pictures, shapes, and the highlightedoutline areas 18101, 18106, 18112, 18125 may be embedded as part ofcontent item area 208.

The element area 18101 may comprise the found and calculated elementarea 18102 and the derived element area 18103. The element area 18101,comprised on the background area 208 may comprise text or graphic,symbol or other data 18104 also comprised on the background area 208 andin general proximity (or not, and inside or outside) the element are18101. The found and calculated element area 18102 or the derivedelement area 18103 may be displayed as a layer in front of thebackground layer 208 for display purposes, and which may comprisedisplay text, graphics or data 18116 in an element area display layerand which may be displayed, viewed, and/or receive interaction.

The data 18116 displayed in either the found or derived element areasmay have a logical association and/or visual association and/orpositional association with data 18104 and which may be comprised in thebackground area 208. The data 18116 may be a data variable value, that,in some embodiments, may comprise a plurality of individual datavariable values 18117, 18118, 18119, 18120, 18121, and which may bejoined together with a dash “-” (or space(s) or other character(s) orsymbol(s) or combination) to create one overall derived data variablevalue 18116 for example, for display purposes.

Data 18104 may be a data variable label (or derived data variable label)that, in some embodiments, comprises a plurality (for example, five)individual data variable labels 18111, 18112, 18113, 18114, 18115, andwhich may be joined together with a dash “-” (or space(s) or othercharacter(s) or symbol(s) or combination) to create one overall datavariable label 18104 for example, for display purposes. Each individualdata label may be associated with an individual data value. Datavariable value 18117 may be associated with data variable label 18111,data variable value 18118 may be associated with data variable label18112, data variable value 18119 may be associated with data variablelabel 18113, data value 18120 may be associated with data variable label18114, data variable value 18121 may be associated with data variablelabel 18115. A practical example for data variable label 18111 may be,for example, “Date” whereas its associated data variable value could be“1 Jan. 2020”.

The element area 18106 may comprise found element area 18108 and derivedelement area 18110. The element area 18106, comprised on the backgroundarea 208 may comprise text, graphics, symbols and/or other data 18107also comprised on the background area 208 and in proximity (inside oroutside) the element area 18106. Found element area 18108 or the derivedelement area 18110 may be displayed as a layer in front of thebackground layer 208 for example, for display purposes, and may comprisedisplay text, graphics or data 18109 in this layer, that may bedisplayed and viewed.

The data 18109 displayed in the found or derived element areas may havea logical association with the data 18107 and which may be comprised inthe background area 208. The data 18109 may be referred to as a datavalue, and which may comprise a plurality of (for example, four)individual values 18129, 18130, 18131, 18132, and which may be joinedtogether with a dash “-” (or space(s) or other character(s) or symbol(s)or combination) to create one overall derived value 18109 for displaypurposes. The data 18107 may be referred to as an overall data label,and which may comprise a plurality of (for example, four) individualdata labels 18125, 18126, 18126, 18128 and which may be joined togetherwith a dash “-” to create one overall data label 18109, for example, fordisplay purposes. Each individual data label may be associated with anindividual data value. Data value 18129 may be associated with datalabel 18125, data value 18130 may be associated with data label 18126,data value 18131 may be associated with data label 18127, data value18132 may be associated with data label 181128. A practical example fordata label 18125 could be “Date” whereas its associated data value couldbe “1 Jan. 2020”.

In another embodiment, element area 18122 (comprised within backgroundarea 208) may comprise found element area 18124 whereby found elementarea 18124 may be displayed as a layer in front of background layer 208for example, for display purposes, and which may comprise display textor graphics 18123. Referring also to element areas 701 & 702 (refer toFIG. 7 ) 1605 and 1609 (refer to FIG. 16A and to FIG. 16B), and elementarea interactivity data store 803 (referring to FIG. 8A).

The element area 18122 and data item 18123 may be comprised in thebackground area 208. The found and calculated element area 18124 may bedisplayed as a layer in front of the background area and where the foundelement area has display properties such that it may have somesemitransparent color and or other visual effects applied such that thebackground data 18123 may be still visible. The element area may alsosupport properties that enable it to respond to a user select action(voice command, touch command, or mouse command click).

The element area 18122 may also support a derived element area 18126.This derived element area 18126 may be displayed as a layer in front ofthe background area and where the found element area has displayproperties such that it may have some semitransparent color and or othervisual effects applied such that the background data 18123 may be stillvisible.

In another embodiment element area 18122 many comprise the found andcalculated element area 18124, and the derived element area 18126. Thefound element area 18124 and the derived element area 18126 may both bedisplayed as a layers in front of the background layer 208 for displaypurposes, and with either the found element area being in front ofderived element area 18126, or the derived element area 18126 may be infront of found element area 18124. The found element area 18124 andderived element area 18126 may also both comprise display propertieswhich enable the visual display of data 18123 (i.e. the data 18123 isnot being comprised within the background area 208, but in the found18124 element area visual display properties of either found area 18124or the derived area 18126. A practical example for the found 1824 orderived area 18126 is to display START as a data variable value whereasits associated data variable label could be FUNCTION which can be anartifact contained in the overall background area 208.

The data values 18116, 18117, 18118, 18119, 18120, 18121, 18109, 18129,18130, 18131, 18132, 18123 may be generated via user input orprogrammatically by other user interface modules 1302, 1308 (referringto FIG. 13 ), 1403 (referring to FIG. 14 ) and may be supported by thefixed content user data store 1313, referring to FIG. 13 .

Data variable values 18116, 18117, 18118, 18119, 18120, 18121, 19109,19129, 19130, 19131, 19132 may be generated by programmatic variablesrules which may be associated with the fixed layout components 201, andwhere the variable rules output data values are then displayed as partof the specific found or derived element areas via a logical associationdata reference comprised in the fixed-layout component definition dataand metadata 806 in general and specifically the association data 803(referring to FIG. 8A). The data variables rules with a set/fixed valuemay be termed set variables (SV). The data variables rules with anassociation for a user element area interaction may be termed userrequested variables (URV). User requested variables rules and setvariables rules may then support the calculation of derived variablesrules data (DV), and on the calculation of at least a portion of derivedvariables data, then derived-variable-labels data (DVL) may be generatedfrom user (URV), set (SV) and derived (DV) variables data or otherderived variable labels data (DVL).

Any individual variable value item 18116 . . . 18121, 18129 . . . 18132,(referring to FIG. 18K) may be a user requested variable data or aderived variable data, or a derived variable label data. The values maybe assembled as an overall variable data 18116, that may be defined asVALUE-1-VALUE-2-VALUE-3-VALUE-4-VALUE5. In this embodiment there are aplurality of variables (for example, 5), which may result in atheoretical number of 120 different combinations or versions of derivedvariable label value, and so each of the 120 examples may be defineduniquely with its own variables rule. Any user variable, derivedvariable, or derived-label values may be a component of an overall value18116, 18108.

FIG. 19A is a high-level flow diagram illustrating an exemplary processfor an automatic finding and calculation of element item areas andassociated data for data stores, according to an embodiment of theinvention. According to the embodiment, an example of process flow stepsfor automatic finding and calculation of element item areas and at leasta portion of associated data for data stores 806 (referring to FIG. 8A)is shown. Process 1900 starts at step 1901 to automatically find andcalculate the fixed-layout element item areas and associated data andthen to provide the data (and derived data) which may be required fordimensions and positional data store 802 and which may then be used infinal fixed-layout package data store 806. An alternative may be for theuser to manually calculate the necessary dimensional and positional data806. The process may be started 1901 by the initialization 1902 of asearch application (which may be either an online application or anative/installed application) and where the overall fixed-layoutcomponent item 208 may be loaded and displayed to a user. The user maythen select if a single element item area must be identified or ifmultiple adjacent areas 1801, 1802, 1803, 1804, 1813, 1815, 1817 in step1903 are to be identified. The user may then commence a single elementarea search by selecting an area-specific physical location, any pointlocation 1805 inside the area 1801 via input received from a computermouse pointer or finger touch control or other device input method. Inarea 1801, the search algorithm may then commence the search in manydirections 1803, 1804, 1805, 1805 to determine calculations datanecessary to support the new calculated area perimeter of 1807 (thedashed line figure). At least a portion of the data andcalculated/derived data for the specific area 1807 may be saved to thedimensions and position data store 802. If a search for a single areawas initiated initially, then the search process may be completed. If asearch for multiple adjacent areas was initiated (referring embodimentareas 1802, 1803, 1804 or 1813, 1815, 1817), then step 1907 continuesprocessing at step 1905 where the search algorithm may moveautomatically onto the next associated adjacent area (in this embodiment1803 and 1804, or 1815, 1813 and 1804) and identify at least a portionof the required data where the at least a portion may be saved in thedimensions and positional data store 802. For multiple adjacent areasearch, the user may then commence the search by selecting anarea-specific physical location, any point location 1812 inside the area1802 via input received from a computer mouse pointer or finger touchcontrol or other device input method, and selecting the general searchdirection 1811 for the automatic search. The general search directiondefines the general direction of a search (for adjacent cells), and maybe in a specific direction from a start point; left, right 1822, up,down 1811, etc. A general search direction may also be set automaticallyso that at least a portion of possible directions (up 1824, down 1811,left 1823, right 1822) may checked automatically to identify at least aportion of the adjacent cells in each specific cell direction.

In area 1802, the search algorithm may then commence the search withinthat area firstly (in the same way as outlined for area 1801 above) todetermine calculations for that first element area, and then for thealgorithm to progress in the defined direction 1811 to define elementareas 1803 and 1804 in this illustrated embodiment. The iterativeprocess 1908 for multiple element areas will continue until at least aportion of adjacent areas are processed and the iterative process ends1909 and at least a portion of the data may be processed and stored inthe element area dimensions data store 802, which may be then processedfurther to create the final fixed-layout component definition data 806.

FIG. 19B is high-level flow diagram illustrating at a high level anotherexemplary process for an automatic finding and calculation of found andthen derived element item areas using configurable using general andenhanced search logic and with associated data for data stores,according to an embodiment of the invention. According to theembodiment, an example of process flow steps for automatic finding andcalculation of element item areas and at least a portion of associateddata for data stores 806 (referring to FIG. 8A) is shown. Process 1900starts at step 1901 to automatically find and calculate the fixed-layoutelement item areas and associated data and then to provide data (andderived data) that may be required for dimensions and positional datastore 802 and that may be used in final fixed-layout package data store806. In another embodiment, dimensional and positional data 806information may be received form a user device. The process is started1901 by the initialization, in step 1902, of a search application (whichmay be either an online application or a native/installed application)and where the overall fixed-layout component item 208 may be loaded anddisplayed to a user.

In a next step 1910, a number of general search logic settings may bereceived from a user device and relating to the found and calculatedelement areas.

In a next step 1911, a range of advanced configuration settings may beprovided relating to enhanced search logic to enable search across oneor many color changes and also to enable the creation of derived elementareas and where the associated detailed settings may be received from auser device.

In a next step 1903, a selection may be received, from the user device,indicating if a single element item area must be identified or ifmultiple adjacent areas 1801, 18021, 18031, 18041, 1813, 1815, 1817(referring to FIG. 18A) in step 1903 are to be identified. A singleelement area search may commence by receiving a selection, from the userdevice, of an area-specific physical location, any point location 1805inside the area 1801 via input received from a computer input device.

In a next step 1905 at area 1801, the search algorithm may then commencethe search in many directions 1803, 1804, 1806, 1807 to determinecalculations data necessary to support a new calculated area perimeterof 1825 (the dashed line figure).

In a next step 1906, at least a portion of the data andcalculated/derived data for the specific area 1825 may be saved to thedimensions and position data store 802, 803, 804, 805, 807, and 806(referring to FIG. 8B).

If a search for a single area was previously initiated at step 1903 andverified at step 1907, then the search process may be completed at step1909. If a search for multiple adjacent areas was initiated at step 1903(referring to embodiment areas 18021, 18031, 18041 or 1813, 1815, 1817),then step 1907 may continue processing at step 1905 where the searchalgorithm may move automatically onto the next associated adjacent area(in this embodiment, areas 18031 and 18041, or 1815 and 1813, 1804, andso forth) and identify at least a portion of the required data where theat least portion may be saved in the dimensions and positional datastore 802. For multiple adjacent area search, the user may then commencethe search by selecting an area-specific physical location, any pointlocation 1812 inside the area 1802 via input received from a computermouse pointer or finger touch control or other device input method, andselecting the general search direction 1811 for the automatic search.The general search direction defines the general direction of a search(for adjacent cells) and may be in a specific direction from a startpoint; left, right 1822, up, down 1811, and so forth. A general searchdirection may also be set automatically so that at least a portion ofthe possible directions (up 1824, down 1811, left 1823, right 1822) maycheck automatically to identify at least a portion of the adjacent cellsin each specific cell direction.

In area 18021, the search algorithm may then commence a search(similarly to area 1801 above) to determine calculations for the firstelement area, and progress in the defined direction 1811 to defineelement areas 18031 and 18041. The iterative process 1908 for multipleelement areas may continue until at least a portion of adjacent areasare processed and the iterative process ends at step 1909 and at least aportion of the data may be processed and stored in the element areadimensions data store 802, which may be then processed further to createthe final fixed-layout component definition data 806.

Fixed-Layout Component Creation

FIG. 24A is a block diagram illustrating an exemplary systemarchitecture 2400 for creating the fixed-layout component packages,according to a preferred embodiment of the invention. According to theembodiment, creation of fixed-layout components may comprise:fixed-layout content export parameters designator 2403 may designate aquality (for example, a level of image pixilation, image grain, and thelike), resolution (for example, a high or low number of pixels), andfile size (for example, kilobyte (kB)/megabyte (MB), etc.) of afixed-content component, prior to the actual creation of fixed-layoutcomponents. User devices 2401 a-n may receive, send, and set parametersassociated to fixed-layout content via accessing export parametersdesignator 2403 via, for example, cloud network 2402 (or network 31),prior to export manager 2404 importing, processing, and exportingfixed-layout content items (for example, a selection of fixed-contentfiled resident on storage device HDD 52 imported from the file system,and processed by system 2400). Fixed-layout content export manager 2404may import source files(s) in a plurality of source formats known in theart (e.g. PDF, Microsoft™ Word documents, and the like) that maycomprise a plurality of pages, and then analyze and export eachfixed-layout content item (e.g. a fixed-content layout graphic such asPNG, JPEG, and the like). Accordingly, the fixed-layout content exportprocess may result in one or more associated items (e.g. PNG, JPEG, andthe like) for each page of the plurality of pages of the original sourcefile. Interaction requests from one or more user devices 2401 a-n may bereceived by export manager 2404 to: identify one or more input files(for example, a plurality of PDF files); to process and start anautomatic process of importing the input files (i.e. “the PDFs”) andexporting the components (i.e. “the PNGs”). Content metadata manager2405 may receive exported files from export manager 2404 and createassociated additional metadata to the exported fixed-layout item.

Element finder 2406 may automatically find dimensions of a single shapearea or a range of adjacent areas for areas embedded in the fixed-layoutcomponent item which has been exported via export manager 2404 (e.g.PNG, JPEG, etc.). Interaction requests may be received from one or moreuser devices 2401 a-n by export manager 2404 to, for example, select atwo-dimensional (2D) area for where element finder 2406 may commence asearch for one or more shape areas. Element metadata manager 2407 mayreceive one or more 2D x-y coordinates data from element finder 2406 andperform calculations on the data (for example, as described in FIG. 5A,FIG. 10 , and FIG. 18A).

Element creator 2408 may allow a creation of areas/shapes that may be anoverlay displayed on top of the fixed layout exported content componentitem. For example, as an additional layer of interactive componentsdirectly associated to the fixed-layout content with associatedfunctions.

File loader 2409 may upload exported files from a storage device (suchas HDD 52), for example, upon receiving a request and location from auser device 2401 a-n, and place them into system 2400 for furtherprocessing by client metadata module 2405. File viewer 2410 operates asa mechanism to view files, as is known in the art.

In some embodiments, at least system components 2403, 2404, 2404, 2405,2406, 2407, 2408, 2409, 2410 may reside and execute completely on a userdevice 2401 a in one complete system.

FIG. 24B is another block diagram illustrating an exemplary systemarchitecture 2400 for creating the fixed-layout component packages,according to a preferred embodiment of the invention. According to theembodiment, creation of fixed-layout components may comprise:fixed-layout content export parameters designator 2403 may designate aquality (for example, a level of image pixilation, image grain, and thelike), resolution (for example, a high or low number of pixels), andfile size (for example, kilobyte (kB)/megabyte (MB), etc.) of afixed-content component, prior to the actual creation of fixed-layoutcomponents. User devices 2401 a-n may receive, send, and set parametersassociated to fixed-layout content via accessing export parametersdesignator 2403 via, for example, cloud network 2402 (or network 31),prior to export manager 2404 importing, processing, and exportingfixed-layout content items (for example, a selection of fixed-contentfiled resident on storage device HDD 52 imported from the file system,and processed by system 2400). Fixed-layout content export manager 2404may import source files(s) in a plurality of source formats known in theart (e.g. PDF, Microsoft™ Word documents, and the like) that maycomprise a plurality of pages, and then analyze and export eachfixed-layout content item (e.g. a fixed-content layout graphic such asPNG, JPEG, and the like). Accordingly, the fixed-layout content exportprocess may result in one or more associated items (e.g. PNG, JPEG, andthe like) for each page of the plurality of pages of the original sourcefile. Interaction requests from one or more user devices 2401 a-n may bereceived by export manager 2404 to: identify one or more input files(for example, a plurality of PDF files); to process and start anautomatic process of importing the input files (i.e. “the PDFs”) andexporting the components (i.e. “the PNGs”). Content metadata manager2405 may receive exported files from export manager 2404 and createassociated additional metadata to the exported fixed-layout item.

Element finder 2406 may automatically find dimensions of a single shapearea or a range of adjacent areas for areas embedded in the fixed-layoutcomponent item which has been exported via export manager 2404 (e.g.PNG, JPEG, etc.). Interaction requests (for general search, advancedsearch and other parameters) may be received from one or more userdevices 2401 a-n by export manager 2404 to, for example, select atwo-dimensional (2D) area for where element finder 2406 may commence asearch for one or more shape areas.

Element metadata manager 2407 may receive one or more 2D x-y coordinatesdata from element finder 2406 and perform calculations on the data (forexample, as described in FIG. 5A, FIG. 10 , FIG. 18A). Thesecalculations can enable the creation of the found/calculated elementarea(s) as well as any requested derived element areas.

Element creator 2408 may allow creation of areas/shapes that may be anoverlay displayed on top of the fixed layout exported content componentitem. For example, as an additional layer of interactive componentsdirectly associated to the fixed-layout content with associatedfunctions. The element creator 2408 may allow the creation offound/calculated or derived element areas of both categories of elementareas.

File loader 2409 may upload exported files from a storage device (suchas HDD 52), for example, upon receiving a request and location from auser device 2401 a-n and place them into system 2400 for furtherprocessing by client metadata module 2405. File viewer 2410 operates asa mechanism to view files, as is known in the art.

A variables rules library data repository 2411 maybe provided which mayallow the element creator 2408 to associate specific rules via metadata(referring from this library to specific found/calculated or derivedelement areas.

Element area variables rules configurator 2412 may receive requests fromone or more user devices 2401 a-n to associate data variables rules witheither found/calculated or device or both categories of element areas.User devices 2401 a-n may select any random location/positionco-ordinate X_(r), Y_(r) which resides inside a found, calculated orderived element area (referring to FIG. 18H) depending on which areatype the user device wishes to associate the specific area rule (s).

A variable rules library may be provided in the data store 2411. Thevariables rules configurator 2412 may then associate specific variablesrules from the variable rules library with specific element areas(either found/calculated or derived or both) and wherein the associatedmetadata and the specific associated variables rules data can then becopied from the overall variable rules library 2411 and the data canthen be copied into the specific metadata data store 807, and which isthen combined with the other data stores 801, 802, 803, 804 (referringto FIG. 8B) to then result in the creation of the coverall fixed-layoutcomponent definition data store 806 (referring to FIG. 8A).

In another embodiment, system component comprising 2403, 2404, 2405,2406, 2407, 2408, 2409, 2410, 2411, and 2412 may reside and execute on asingular user device 2401 a.

FIG. 25 is an exemplary process for creation of an exported fixed-layoutcontent item, database, and files 801. According to an embodiment, agraphic file/image (e.g. PNG, JPEG, etc.) may be exported from a sourcefile (for example, a PDF file). According to the embodiment, for n pagesin the source file, the export may provide n number of graphic/files(e.g. PNG files) export files. In some embodiments, any number ofgraphic/files may be exported for a source file (e.g. from a single PDF)page such that the graphics may be re-assembled dynamically (or usingtiling techniques) into one overall seamless graphic presented to adisplay of, for example, user device 2401 a, such that an end user maynot be aware that the graphic presented may be a range of smaller filesdynamically presented together to give a seamless and unified view ofthe original PDF page. Accordingly, a request to commence process 2501may be received from, for example, user-device 2401 a.

Accordingly, in step 2503, a request from user-devices 2401 a-n may bereceived, at files viewer module 2410, to organize at least a portion ofone or more fixed-layout content source files 2502 into a fixed-layoutbatch source content location 2504 and non-batch 2508 source contentfiles. A batch of fixed-source content files may refer to a grouping offiles in a location in a file management system such that the groupingof files may be loaded as a group or batch and where the grouping may beprocessed automatically, for example, one by one, until at least aportion of files in the batch are processed. Examples of batch contentfile types may include, but not limited to, Adobe™ PDF files, Microsoft™Word DOCX (DOC and other variants) and image types, such as, PNG, JPEG,TIFF, and the like. Examples of non-batch content files may include, butnot limited to, Adobe™ Photoshop™ (PSD), Adobe™ InDesign™ (IDD),CorelDraw™ (CDR), and the like.

In a next step 2505, export parameters designator 2403 may configuresystem 2400 to define required parameters on content export (forexample, at least quality, resolution, color, and other parameters asdescribed earlier). Export parameters designator 2403 may receive one ormore requests from, for example, user devices 2401 a relating toparameters which needs to be set, such as, viewing quality (e.g. sharpor dull text on a graphic, which may be a function of pixel resolutionand other parameters) of the fixed-layout component, which in turn mayrelate to dimensions and resolution (pixels size width by height) of theexported content component. The quality parameters may result in varyingfile sizes (kB, MB, etc.) of the files that are exported. Once step 2505is complete, an automatic content export processing step 2506 may beinitiated by, for example, a request from user device 2401 a.Accordingly, content export manager 2404 may receive a request from oneor more user devices 2401 a-n to load one or more source file from thefixed-layout source content files 2504. Content export manager 2404 maythen create a new file (typically for each page of the source inputfile; however, in some embodiments, there may be more than image, asdiscussed previously). In a next step 2506 additional metadata 801 maybe created and associated to files created from the automatic contentexport processing. An example of metadata may be a syntax text filewhich may comprise a definition of how individual pages are grouped orreferred to each other to re-create/represent the original source PDFfile. Other metadata may also be added (for example, metadata associatedto project details, project ID, or other descriptive informationdescribing, linking, sequencing, or other aspects of images and pages).For example, if an original PDF had, for example, ten pages, anassociated metadata file may define which exported files may make-up theoriginal PDF pages and arrange them in a correct original sequence. In anext step 2507, content metadata processing may commence whereby contentmetadata manager 2405 may create and save any associated metadatafiles/data with the exported fixed-layout content files (e.g. images) tothe fixed-layout exported content & metadata data store 805.

In some embodiments, for non-batch files 2508, other programs (e.g.Adobe™ Photoshop™, CorelDraw™, etc.) may be used to provide a supervisedexport at step 2509 via semi-automatic or manual content exportprocessing of fixed-image layout content files to a desired quality.File loader 2409, on receipt of a request from user device 2401 a, mayupload exported files stored on a storage device (for example, to HDD52), for further processing by client metadata manager 2405, to, forexample, generate additional metadata at step 2507 (as described above).Accordingly, fixed layout exported content and metadata 801 may befurther updated.

FIG. 26A is an exemplary process 2600 for the creation of elements areaitems associated with the fixed layout exported content item. Theprocess starts at step 2602 by presenting, on a display screen of a userdevice, a fixed-layout content file so that element items may beassociated with the fixed-layout content item (for example, by receivingrequests from user device 2401 a. The element finder 2406 may display touser device 2401 a, based on a request from user device 2401 a, a fullcontent item (single file or dynamically re-assembled files). Theelement metadata manager 2407 may receive, from user device 2401 a, arange of configurations relating to how one or more new elements may beconfigured. In a next step, 2603, a plurality of parameters may bedefined to determine how the one or more element items may be presentedto a user interface of a display of, for example, user device 2401 a,and how interaction from user device 2401 a may behave with respect tothe one or more element items. Further, various states associated toelements describing behavior of the element item, may be determinedwithin an overall application system. Element area item configurationproperties, that may be stored as metadata, of the one or more elementsitems, may be: (a) the type of area that is being searched for (e.g. arectangle of any size); (b) defining one or more display color(s) of theelement area for various states; (c) if the element area allows dataentry (e.g. from a user device selecting within an element area of theone or more element areas), and type: select a format e.g. numeric,alphanumeric, or some other predefined data format; (d) the element areamay have additional properties such as: mandatory or non-mandatorydata-entry for an associated element area where data must be entered (ornot), by, for example, a user device of user devices 2401 a-n forvarious states; (e) a pre-configured display of other items within anelement area: such as a string of text, and other related parameters;(f) set display layer association; (g) associating a unique element areareference number; (h) linking element-areas logically such that if datamay be entered in a specific element-area, the next logical associatedelement-area may be then allowed to accept data entry (or not); (i) anynumber of other behaviors determining function for a user interface oruser device display.

The type of element-area being searched (e.g. a rectangle), may be usedby the element finder 2406 to determine a number of and specificelement-area internal search directions (for example, from the searchpoint 1805) that element finder 2406 may use in the search area process.Examples of internal search directions for rectangles are illustrated inFIG. 18, 1803, 1804, 1805 1806 according to one embodiment of theinvention. Areas of different shapes may require a different number ofinternal search directions to ensure that boundaries of an element areamay be identified.

In a next step 2604, a select search start position process for findingthe element area item begins. The element finder 2406 may receive aninput, for example, from a user input device 49 or 50 (for example, auser pointing device, keyboard, touch screen device) associated to userdevices 2401 a that initiates a search process to start. An x-y 2Dcoordinate position of a location associated to the location receivedfrom user interaction, for example, via input device 50, may be providedto the element finder 2406, and must be inside an associated border ofthe element area that may need to be identified, and which may be partof the fixed-layout content item.

In a next step 2505, a find element x-y coordinates begins in order todetermine the element's x-y coordinates for each element definitionpoint (for example, as described in FIG. 7 : 706, 707, 708, 709) on theselected element area (e.g. in a square or a rectangle element area,there are four primary definition points, or corners, by which the areamay be re-created). Element finder 2406 may receive, from user device2401 a, coordinates for an x-y start value from which to commence thearea search. The element finder 2406 may continue processingautomatically until it has identified at least a portion of the x-ycoordinate values for at least a portion of the primary definitionpoints. referring again to FIG. 18 , in an embodiment, outline area 1801may be comprised in overall fixed-layout area 201, whereby a new elementarea to identify may be outline 1825, and whereby element finder 2406may be prioritizing computations to firstly identify the x-y position ofelement definition points 706, 707, 708, 709.

In a next step, 2606, a calculation for element dimensions data maybegin by calculating dimensions data from x-y coordinate data calculatedin step 2605. The element creator 2408 may receive x-y coordinate valuesfrom element finder 2406 to calculate an additional set of data valuesthat may include element area width and height and an actual position ofthe element area with respect to the overall fixed-layout content item.Referring again to FIG. 4 , the embodiment may comprise a calculationfor width 401 and height 402. Referring again to FIG. 5A, the embodimentmay comprise reference point 509 in the element area with respect tofixed-layout area reference point 501. Accordingly, reference points 501and 509 may then allow actual dimensions of an absolute x position 510,and y position 508 of the selected element area. With element area xposition 510 and y position 508, and fixed-layout content item xposition 514 (similarly, 301), and y position 515 (similarly, 302), andwidth 401, and height 402; accordingly, the dimensions may then be usedto calculate derived values of fractions (or percentages when multipliedby 100). Accordingly, at least a portion of x direction dimensions maybe divided by overall x dimension 301 (or 514) to result in a decimalfraction, similarly for x direction dimensions 302 (or 515) to arrive ata decimal fraction.

In a next step 2609, positional, dimensional, derived/fractional(including calculated values) data for items may be saved to elementdata store 805. Element creator 2408 may saves x-y coordinates,calculated and derived fraction data, and resultant data from theelement area properties step 2603. The element creator 2408 may saveassociated data to the element to data store 805. On completion of step2609, element finder 2406 may begin process 2600 at step 2604 foranother selection of a search start position to find another singleelement area request. In some embodiments, for a different element type,processing may begin again at step 2603.

In some embodiments, if element finder 2604 receives a request, from,for example, user device 2401 a, to find a range of adjacent cells (thatis, a plurality of adjacent areas of a fixed-layout content for whichelement areas are desired) in, for example, an external search direction1811 (referring to FIG. 18A) and start position 1812. Element finder2406 may begin at step 2608 to automatically find a next element area.Accordingly, steps 2605, 2606 and 2607 may be repeated until, forexample, element finder 2406 may be unable find any additional adjacentelement areas. Referring again to FIG. 18 , according to the embodiment,if a find element area 1812, for example, as selected by user device2401 a, with a goal to find element areas within find area 1808, elementfinder 2406 may then iterate automatically to find the next area 1809and 1810 automatically, and from the outlined areas 1802, 1803, 1804comprised in fixed-layout content item 201. Referring again to FIG. 18 ,search direction 1822 illustrates a different search direction, where aselection 1820 (for example, as selected by user device 2401 a) mayinitiate a search, by element finder 2406, to iteratively identifyelement area 1818, 1816, and 1814.

FIG. 26B is a flow diagram illustrating another exemplary process forlayering additional objects, or object areas, over fixed-layout contentitems and associated data stores, configuring found, calculated andderived element areas, configuring specific advanced search logic, andassociating derived variables and logic rules to the “areas” accordingto an embodiment of the invention. According to the embodiment, process2600 illustrates a creation of elements area items associated with thefixed layout exported data store 806.

The process starts at step 2602 by presenting, on a display screen of auser device, a fixed-layout content file so that element items may beassociated with the fixed-layout content item (for example, by receivingrequests from user device 2401 a). The element finder 2406 may displayto user device 2401 a, based on a request from user device 2401 a, afull content item (single file or dynamically re-assembled files).

In a next step 2603 the element metadata manager 2407 may receive, fromuser device 2401 a, a range of configurations relating to how one ormore new elements may be configured, including for user display andinteractivity properties. Further in step 2603, a plurality ofparameters may be defined to determine how the one or more found elementitems may be presented to a user interface of a display of, for example,user device 2401 a, and how interaction from user device 2401 a maybehave with respect to the one or more element items. Further, variousstates associated with the found elements areas describing generalbehavior, visual behavior or user behavior of the element item, may bedetermined within an overall application system. Element area itemconfiguration properties (for both found/calculated or derived or both),that may be stored as meta data, for one or more elements items, may be:(a) the type of area that is being searched for (e.g. a rectangle of anysize); (b) defining one or more display color(s) (external border, orinternal area) of the element area for various states; (c) if theelement area allows data entry (e.g. from a user device selecting withinan element area of the one or more element areas), and type: select aformat e.g. numeric, alphanumeric, or some other predefined data format;(d) the element area may display certain defined data value(s), (e)element area category (i.e. found/calculated or derived) may determinewhich of these elements will display data or allow a user interaction orboth (f) the element area may have additional properties such as:mandatory or non-mandatory data-entry for an associated element areawhere data must be entered (or not), by, for example, a user device ofuser devices 2401 a-n for various states; (g) a pre-configured displayof other items within an element area: such as a string of text, andother related parameters; (h) set display layer association; (i)associating a unique element area reference number; (j) linkingelement-areas logically such that if data is entered in a specificelement-area, the next logical associated element-area is then allowedto accept data entry (or not); (k) any number of other behaviorsdetermining function for a user interface or user device display.

The type of element-area being searched for (e.g. a rectangle), may beused by the element finder 2406 to determine a number of and specificelement-area internal search directions (for example, from search point1805) that element finder 2406 may use in the search area process.Examples of internal search directions for rectangles are illustrated inFIG. 18A, 1803, 1804, 1805 1806 according to one embodiment of theinvention. Areas of different shapes may require a different number ofinternal search directions to ensure that boundaries of an element areamay be identified.

In a next step 2613 the element metadata manager 2407 (referring to FIG.24A) may receive, from user device 2401 a a number of specificconfiguration settings from an overall configuration library that willbe used to determine how the derived element areas (if required) will becalculated/derived from the found and calculated element areas. In step2613, a plurality of parameters may be defined (via request from userdevice 2401 a) to determine how the one or more derived element items1861, 1863, 1865, 1867, 1869, 1871 1873, 1875, 1877, 1870 (referring toFIG. 18D) may be automatically calculated and also what userinteractivity and display properties that may need to be configured forderived areas (via request from user device 2401 a).

In a next step 2614, the element metadata manager 2407 may receive, fromuser device 2401 a a range of configuration settings that may be used toconfigure either standard and/or advanced search logic properties forcertain search directions, to allow the finding of element areas 1801(referring to FIG. 18H) that may be spread across multiple backgroundareas 18160, 18162, 18163, 18170 (referring to FIG. 18H), and advancedsearch logic may relate to finding areas which may have multiplebackground areas. The element metadata manager 2614 may also receivefrom user device 2401 a . . . n configuration settings relating to thecreation of derived element areas 18317 (referring to FIG. 18B), 1832,and 1850 (referring to FIG. 18A).

In a next step 2604, a select search start position process for findingthe element area item begins. The element finder 2406 may receive aninput, for example, from a user input device 49 or 50 (for example, auser pointing device, keyboard, touch screen device) (referring to FIG.23 ) associated to user devices 2401 a that initiates a search processto start. An x-y 2D coordinate position of a location associated to thelocation received from user interaction, for example, via input device50 (referring FIG. 23 ) may be provided to the element finder 2406, andmust be inside an associated border of the element area that may need tobe identified, and which may be part of the fixed-layout content item.

In a next step 2605, a find element x-y coordinates begins in order todetermine the element's x-y coordinates for each element definitionpoint (for example, as described in FIG. 7 : 706, 707, 708, 709) on theselected element area (e.g. in a square or a rectangle element area,there are four primary definition points, or corners, by which the areamay be re-created). Element finder 2406 may receive, from user device2401 a, coordinates for an x-y start value from which to commence thearea search. The element finder 2406 may continue processingautomatically until it has identified at least a portion of the x-ycoordinate values for at least a portion of the primary definitionpoints. Referring again to FIG. 18A, in an embodiment, outline area 1801may be comprised in overall fixed-layout area 201, whereby a new elementarea to identify may be outline 1808, and whereby element finder 2406may be prioritizing computations to firstly identify the x-y position ofelement definition points 706, 707, 708, and 709.

In a next step, 2606, a calculation for the automatically found elementdimensions data may begin by calculating dimensions data from x-ycoordinate data calculated in step 2605. The element creator 2408 mayreceive x-y coordinate values from element finder 2406 to calculate anadditional set of data values that may include element area width andheight and an actual position of the element area with respect to theoverall fixed-layout content item. Referring again to FIG. 4 , theembodiment may comprise a calculation for width 401 and height 402.Referring again to FIG. 5A, the embodiment may comprise reference point509 in the element area with respect to fixed-layout area referencepoint 501. Accordingly, reference points 501 and 509 may then allowactual dimensions of an absolute x position 510, and y position 508 ofthe selected element area. With element area x position 510 and yposition 508, and fixed-layout content item x position 514 (similarly,301), and y position 515 (similarly, 302), and width 401, and height402; accordingly, the dimensions may then be used to calculate derivedvalues of fractions (or percentages when multiplied by 100).Accordingly, at least a portion of x direction dimensions may be dividedby overall x dimension 301 (or 514) to result in a decimal fraction,similarly for x direction dimensions 302 (or 515) to arrive at a decimalfraction.

In a next step 2609, at least a portion of positional and dimensional,calculated (including for automatically found area calculated values)data for items may be saved to element at least a portion of data store805. Element creator 2408 may save (to data store 805) at least aportion of x-y coordinates, calculated and derived (dimensional,position) data (for both found and/or derived element area), andresultant data from the element area properties step 2603 including atleast a portion of the settings for derived area requirement and alsothe applied search logic. The element creator 2408 may save at least aportion of area (found and derived), associated metadata, and any otherrelated associated data to the element to data store 805. On completionof step 2609, element finder 2406 may begin process 2600 at step 2604for another selection of a search start position to find another singleelement area request.

In another embodiment, on completion of step 2609, element finder 2406may begin process 2600 at step 2603 where a different element area typeand other user or display properties may be selected via the user device2401 a.

In another embodiment on completion of step 2609, element finder 2406may begin process 2600 at step 2613 where different properties may bedefined for derived element areas which may be calculated from foundelement areas, referring to FIG. 18C

In another embodiment on completion of step 2609, element finder 2406may begin process 2600 at step 2614 where different properties may bedefined for the search logic which enables the finding of found elementareas which may be spread across multiple background areas, referring toFIG. 18H.

It should be noted that in other process flow embodiments that steps2603, 2613, 2614 may have alternate sequence before commencement of step2604. One embodiment could be step 2603, followed by step 2614, followedby step 2613, then commence step 2604. Another embodiment could be step2602, then step 2614, then step 2613, then step 2603, then commence step2604.

In another embodiment (referring to FIGS. 26A and 18H), if elementfinder 2604 receives a request from, for example, user device 2401 a, tofind a specific number of element areas, (for example total quantity of3); 1802, 1803, 1804 (referring to FIG. 18J), (at search start 1812)from a total range of 6 adjacent areas 1802, 1803, 1804, 1851, 1852,1853, 1856 (referring to FIG. 18J), i.e., a plurality of adjacent areasof a fixed-layout content for which element areas are desired—in, forexample, an external search direction 1811 (referring to FIG. 18J). Onceeach element area find is complete, the element finder 2406 may beginagain at step 2608 to automatically find a next element area.Accordingly, steps 2605, 2606, 2612 and 2607 may be repeated until thespecified number of element areas 1802, 1803, 1804 (referring to FIG.18J) have been found 1808, 1809, 1861. Each of the automatically found1802, 1803, 1804 element areas may then utilize the same percentage orpixel dimensions (values or %) to calculate the derived areas 1858, 18591860 (if required). The adjacent element areas search would utilize thesame parameters for search logic properties 2614 via the request fromthe user device 2401 a. The adjacent element areas search would alsoutilize the same parameters for the creation of the derived areas 1858,1859, 1860.

In some embodiments, if element finder 2604 receives a request, from,for example, user device 2401 a, to find a range of adjacent cells tothe end of that list (that is, a plurality of adjacent areas of afixed-layout content for which element areas are desired) in, forexample, an external search direction 1864 (referring to FIG. 18J) andstart position 1863. Element finder 2406 may begin at step 2604 toautomatically find a next element area. Accordingly, steps 2605, 2606,2612, 2608, 2609 may be repeated 2608 until, for example, element finder2406 may be unable find any additional adjacent element areas. Referringagain to FIG. 18J, according to the embodiment, if a find element area1812, for example, as selected by user device 2401 a, with a goal tofind element areas within find area 1808, element finder 2406 may theniterate automatically to find the next area 1809 and 1810 automatically,and from the outlined areas 1802, 1803, 1804 comprised in fixed-layoutcontent item 201.

Referring again to FIG. 18J, search direction 1822 illustrates adifferent search direction, where a selection 1820 (for example, asselected by user device 2401 a) may initiate a search, by element finder2406, to iteratively identify element area 1818, 1816, and 1814.

In next step 2612, a calculation for derived element area(s) may becompleted (if required via input device 2401 a request at step 2613previously). The derived element area settings referring to FIG. 18Cwill comprise the percentage or pixel dimension 1835, 1840, 1843, 1849variations which are applied to the dimensions of the automaticallyfound and calculated area in step 2606. The percentage or pixeldimensions adjustments may be positive or negative (referring to FIG.18C; 1855 for negative, reduction and 1856 for positive, increase) foreach search direction resulting in the new additional derivedcalculations for each search direction 1803, 1804, 1806, 1807 (referringto FIG. 18C) being calculated. The positive or negative adjustments forat least a portion of search directions may result in a large range ofscenarios; refer to example embodiments 1861, 1863, 1865, 1869, 1871,1873, 1875, 1877, 1879 referring to FIG. 18D. Referring again to FIG.18C the target element areas 1830, 1801 may result in automaticallyfound element areas, 1831, 1849 and which may then result in calculation2612 of the new derived element areas 1832, 1850. Referring to FIG. 18D,the target element areas 1860, 1862, 1864, 1866, 1868, 1870, 1872, 1874,1876, 1878 may have resulted in the generation of the derived elementareas 1861, 1863, 1865, 1867, 1867, 1869, 1871, 1873, 1875, 1877, 1879.The element creator 2408 may save at least a portion of area derived,associated metadata, and any other related associated data to theelement to data store 805.

In a next step 2615 (referring to FIG. 26A) and which could occur at anytime after the step 2612 the element creator 2412 may receive arequest(s) from a user device 2401 a to associate specific variablesrules with a specific element area (found/calculated or derived), andwhere the data stores 807, 805, and 806 are updated. The user device2401 a-n selects any random location (X_(r) Y_(r)) (r=random) 18180(referring to FIG. 18H) inside a previously specified found, calculatedor derived element area specific rule(s). The search process for the(X_(r) Y_(r)) 18180 random location will dynamically identify a newelement area, described as the “temporary” element area, and all theassociated dimensions. The variable rules configurator 2412 will verifythat the random location (X_(r) Y_(r)) “temporary” element areapresented is calculated and verified to be at or just inside or outsidethe boundary of the previously found, calculated or derived element. Theverification process may support an exact match or a pre-definedpercentage of dimensions tolerance positive or negative. If the randomlocation (X_(r) Y_(r)) “temporary” element area is at or inside oroutside the boundary (i.e. within a defined percentage tolerance) of thefound, calculated or derived element, the variable rules configurator2412 then receives a request from device 2401 a . . . n indicatingspecific rule(s) from the rules library 2411 to associate to theselected areas (found, calculated, derived), and the variables rulesconfigurator 2412 then stores the resulting metadata in the data store807 (referring to FIG. 8B). In another embodiment, the presented searchlocation (X_(r) Y_(r)) 18180 may be directly compared to the datapreviously stored in the fixed-layout package data store 805 (referringFIG. 8B) to determine if the location (X_(r) Y_(r)) is at or inside thefound or derived element area which is targeted for the association ofvariables rule(s).

In a next step 2610, the element creator 2408 updates the overall fixedlayout content component data store 806 based on updates to any updatesto any of the data stores 801, 805 or 2411.

FIG. 27A is an exemplary process 2700 for a search for x-y coordinatesfor an element area item. In a first step 2701, element finder 2406 mayreceive coordinates, from a user device, associated to an area inside anelement area, element finder may store the x-y coordinates values asstart position coordinates xS-yS. In a next step 2702, element finder2406 may then detect an associated pixel color at the xS-yS location andstore, in database 806, the color data as a start pixel color. Inanother embodiment the start pixel colour may also be stored in anycategory of device memory such as connected memory 43, or nonvolatilememory 44, or other memory types. In a next step 2703, element finder2406 may set an internal search direction associated to the element areatype which has been previously selected in step 2603. Examples ofinternal search direction are illustrated in FIG. 18A, referring to1803, 1804, 1805 1860 from a starting position of 1805 according to oneembodiment of the invention. It should be noted that areas of differentshapes may require a different number of directions to ensure thatboundaries of the element area are identified.

Referring again to FIG. 18A, examples of xS-yS are illustrated at 1805,1812, 1820. Referring again to FIG. 27A, in a next step 2704, elementfinder 2406 may find coordinates for a next adjacent pixel and analyze apixel color at adjacent pixel location. Accordingly, if a first internalsearch direction is a +x direction 1804, then the next pixel coordinatescolor search may be at x-y coordinates equal to x(S+1)−yS coordinateposition. If the first internal search direction was in the −xdirection, for example direction 1805, then the next pixel color checkmay be at coordinates x(S−1)−yS. Further at step 2704, element finder2406 may calculate a next x(S+1)−yS coordinates for search direction1804, element finder 2406 may then reads a current search pixel color atthe x(S+1)−yS coordinates location. In a next step 2705, element finder2406 may compare the current search pixel color to the reference startpixel color and if the two values are the same, then iteration step 2706may be complete. Accordingly, element finder 2406 may be reset tocontinue at step 2704 to execute a next find next pixel coordinate. Itshould be noted that element finder 2406 may continue process iteration2704, 2705, and 2704 until a current search pixel color is not the sameas the start pixel color thereby concluding the specific searchdirection (referring to set internal search direction at step 2703).Referring again to FIG. 18A, a search direction and distance 1804 may beconcluded, thereby defining an x co-ordinate value for a position forelement definition positions 708 and 709. In some embodiments, ifelement finder 2406 sets the next search direction at step 2708 to be −x(referring to direction 1805), then an x coordinate value for elementdefinition positions 706 and 707 may be next identified by elementfinder 2406. And following those two directions, element finder 2406 mayset a next direction as +y (referring to direction 1803), thenidentifying a y coordinate value for position 706, 707, and may thenset, by element finder 2406, a final search direction which may be −ydirection (referring to direction 1806), then the −y coordinate value,for element definition positions 707 and 709, may be identified. In aniteration step 2707, element finder 2406 may process at least a portionof defined search directions until at least a portion of the internalsearch directions are fully completed. On completion of at least aportion of required directions, by element finder 2406, x-y values forelement definition positions 706, 707, 708, 709 may be now identifiedfor the element area, accordingly, element finder 2406 may calculateelement area data points in process step 2606 to calculate elementdimensions data (referring to FIG. 26A).

FIG. 27B is an exemplary process 2700 for a search for x-y coordinatesfor an element area item. In a first step 2701, element finder 2406 mayreceive coordinates, from a user device, associated to an area inside anelement area, element finder may store the x-y coordinates values asstart position 1805 coordinates (X_(s), Y_(s)). In a next step 2702,element finder 2406 may then detect an associated pixel color at the(X_(s), Y_(s)) location 1805 and store, in database 806, the color dataas a start pixel color. In another embodiment the start pixel color mayalso be stored in any category of device memory such as connected memory43, or nonvolatile memory 44, or other memory types. In a next step2703, element finder 2406 may set an internal search directionassociated to the element area type which has been previously selectedin step 2603. Examples of internal search direction are illustrated inFIG. 18H, referring to 1803, 1804, 1806 1807 from a starting position of1805 according to one embodiment of the invention. It should be notedthat areas of different shapes may require a different number ofdirections to ensure that boundaries of the element area are identified.

In a next step 2704, element finder 2406 may find coordinates for a nextadjacent pixel and analyze a pixel color at the adjacent pixel location.Accordingly, if a first internal search direction is a +x direction1804, then the next pixel coordinates color search may be at x-ycoordinates equal to x(S+1)−yS coordinate position. If the firstinternal search direction was in the −x direction, for example direction1807, then the next pixel color check may be at coordinates x(S−1)−yS.Further in step 2704, element finder 2406 may calculate a next x(S+1)−yScoordinates for search direction 1804, element finder 2406 may then reada current search pixel color at the x(S+1)−yS coordinates location. In anext step 2705, element finder 2406 may compare the current search pixelcolor to the reference start pixel color and if the two values the same,the process step iteration 2706 will continue. Accordingly, elementfinder 2406 may be reset to continue at step 2704 to execute a next findnext pixel coordinate. It should be noted that element finder 2406 maycontinue process iteration 2704, 2705, and 27066 until a current searchpixel color is not the same as the start pixel color (or the edge of thefixed area has been reached; referring to FIG. 18I embodiments) therebyconcluding the specific search for a specific direction.

Referring again to FIG. 18H if the element finder 2407 records a colorchange via step 2705, then the element area finder 2406 will progress tothe next step 2709 to analyze the applied search logic.

Referring to FIG. 18H the advanced search logic pre-defined requirementis based on defining the number of color changes required for eachsearch direction NCR_(d(1 . . . n)), and where “NCR” is the number ofcolor change required, and for each search direction “d” and is set forany number of directions 1 to “n” before any search is initiated. Thenumber of actual color changes recorded in any search directionNCR_(d(1 . . . n)), and where “NCA” is the number of actual colorchanges recorded over search time for any number of search directions 1to “n”. The NCA for each search direction will be set to zero for atleast a portion of search directions before a search is initiated. Aseach new pixel color change is recorded for any search in a specificdirection, the value assigned to NCR_(d(1 . . . n)), will increment fromzero (0) to one (1) to two (2) to “n” as the search continues. So forsearch direction 1804, the first pixel color change 18166 (X_(nf1),Y_(nf1)), will set NCR_(d=1804), =1, and for the next color pixel change18175 (X_(nf2), Y_(nf2)) will set NCR_(d=1804), =2 and for the nextpixel change 18167 (X_(nf3), Y_(nf3)) will set NCR_(d=1804), =3. So forsearch direction 1807, the first pixel color change 18165 (X_(nf4),Y_(nf4)), will set NCR_(d=1807), =1, and for the next color pixel change18164 (at coordinates X_(nf5), Y_(nf5)), will set NCR_(d=1804), =2. Thelogic may be then applied to at least a portion of defined searchdirections 1804, 1806, 1807, 1803 for an element area 1801.

The element finder 2406 may commence the search in search direction 1804(d=1804), which comprises three color changes from start location 1805to the border of the required element area at 18167, and the colorchanges are; NCR_(d=1804), =1 for 18166 at coordinates (X_(nf1),Y_(nf1)), then NCR_(d=1804), =2 for 18175 (X_(nf2), Y_(nf2)) andNCR_(d=1804), =3 for 18176 (X_(nf3), Y_(nf3)). The element finder 2406may commence the search in search direction 1807 (d=1807), whichcomprises two color changes from start location 1805 to the border ofthe required element area at 18164, and the color changes are;NCR_(d=1807), =1 for 1816 X_(nf4), Y_(nf4), then NCR_(d=1804), =2 for18164 (X_(nf5), Y_(nf5)).

The element finder 2406 initiates 2708 the next search direction andwith a specific direction being set at step 2703. The process steps2704, 2705, 2709, 2710 will iterate until the search logic (NCAvalue=NCR value) for that specific direction is completed. In aniteration step 2707, element finder 2406 may process at least a portionof defined search directions until the at least portion of the internalsearch directions are fully completed.

The element finder 2406 then uses at least a portion of the X and Yco-ordinates (X_(nf3), Y_(nf3)), (X_(nf7), Y_(nf7)), (X_(nf4), Y_(nf4)),(X_(nf5), Y_(nf5)), (X_(nf6), Y_(nf6)) and then calculates at least aportion of the dimensions and derived calculations (referring to FIG.26A) necessary for the found element area 1849, and with the elementdefinition positions 706, 708, 709, 707.

FIG. 28 is a block diagram illustrating an exemplary system architecture2800 for integrating fixed-layout components with external applicationsaccording to a preferred embodiment of the invention. According to theembodiment, programmatic user interface 2803 may be an application (forexample, workflow and interaction management systems such as SAP™,Siebel™, Oracle″, Genesys™, Cisco Call Manager™, Amazon Connect™,Salesforce.com™, Sugar CRM™, other CRM systems, other custom buildinteraction, customer, and/or workflow management systems) that providesgeneral application functionality and which may be displayed on adisplay screen of a user device 2801 a-n. Programmatic user interface2803 may receive a request (for example, via an application programminginterface, via a user interface, etc.) from a user device 2801 a-n topresent and display an application to a user device display screen.Programmatic user interface module 2803 may any application which hasbeen developed using standard programming techniques where anapplication developer writes application code which may be thencompiled/completed and presents the application logic and display to anend user device. In some embodiments programmatic user interface 2803may be part of a server-based system, for example a SaaS system, as isknown in the art, and the like, whereby a graphical presentation to auser device 2801 a-n has been generated programmatically.

Programmatic user interface 2803 may include the functionality to issuea request from anywhere within its application, to fixed-layout UI (userinterface) 2804. Fixed-layout UI 2804 may then issue a request tofixed-layout processor 2805 to retrieve a fixed-layout component datafrom the fixed-layout component definition data. On receipt of thefixed-layout component data, by the fixed-layout processor 2805, whichin turn may present data to fixed-layout UI 2804, and which may presenton user-devices 2801 a-n. The fixed-layout UI 2804 may then present thecomponent to an associated device display such that the fixed-layoutcomponent may be resized dynamically to fit within the display area(referring to example FIG. 10A: 1001).

Referring again to FIG. 1A, an overall display screen area 101 may havea programmatic area 103 and one fixed-layout display component area 102,as illustrated. Referring again to FIG. 1B, an overall display screenarea 105, programmatic application area 110, and fixed-layout displaycomponent areas 106, 107, 108, 109 is illustrated. In Referring again toFIG. 10A, programmatic area 103 may provide an area/window embedded intoa main programmatic application view with specified programmeddimensions of width 1005 and height 1003, and with position 1004 and1002 relative to the overall display area 101 boundary. Referring againto FIG. 10B, the fixed-layout content component definition configurationdata 806 may be loaded into the fixed-layout area/window outline area1001.

Fixed-layout UI 2804 may issue a request to fixed-layout processor 2805to retrieve the fixed-layout component definition data 806 from the datastore, and present to fixed-layout UI 2804 which may then processes anddisplay definition data 806 on a display screen, of user device 2801a-n, in area/window 1001. Fixed-layout UI 2804 may read and process atleast a portion of definition data 806 for a specific fixed-layoutcomponent which may then enables the specific fixed-layout component tobe reassembled from the component parts of; fixed-layout content item201, element areas defined 202, 203, 204, 205, 206, 207, 208, calculatedfractional dimensions of each element 401, 402, their position 508, 510relative to the fixed-layout area, and user interactivity functionalitydefinitions 802, 803, 806 (that is, part of 806).

Further, fixed-layout UI 2804 may issue a request to fixed-layoutprocessor 2805 to retrieve a specific set of fixed-content user data1313 depending on a requirement of the overall programmatic UI 2803.Fixed-layout component configuration data 806 may comprise uniquemetadata identifiers such that fixed-content user data 1313 may directlyassociated with each specific component in 806. In some embodiments,fixed-layout content component area, and at least a portion of theelement areas, may have associated and unique metadataidentifiers/references. References associated to elements, components(for example, component IDs, element IDs, and related other data definedin metadata) may then be used by fixed-layout processor 2805 to searchfor and retrieve specific fixed-content user data 1313 for element itemscomprised within the fixed-layout component definition 806, and whichmay be part of a specific component definition. Fixed-layout processor2805 may transmit retrieved user data 1313 to the fixed-layout UI 2804for presentation to a display area of, for example, user device 2801 a.

It should be noted that programmatic UI 2803 presentation on a userdevice 2801 a-n may vary significantly in terms of a form factor andorientation of the user device (referring to FIG. 11 : 101, 1101, 1103,1105). Area/window 1001 for each of these examples may have differentdimensions and positional location within the associated device screen(referring to FIG. 11 : 102, 1102, 1104, 1105, 1108). Fixed-layout UI2804 may then display component definition 806, and associated user data1313 inside the areas (referring to FIG. 11 : 102, 1202, 1104, 1105,1108) such that a re-assembly and presentation to the user device may bepositionally and proportionally exact (as illustrated in FIG. 10B: 1001,FIG. 10C: 1009, FIG. 11 : 1102, 1104, 1106, 1108).

The Variables Rules Processor 2807 will receive the user requestedvariables data from the user device 2401 a and process at least aportion of rules associated with the fixed layout component 102 so as togenerate at least a portion of the values for the derived variables, andthen at least a portion of the derived variable labels and submit atleast a portion of the data to the fixed-layout processor 2805. Thefixed-layout processor 2805 may then update the visual displayproperties of the element areas (found or derived) and to display atleast a portion of the values in the relevant element areas.

FIG. 29 is a flow diagram illustrating an exemplary process forautomatic execution of variables rules logic and which can be associatedwith found, calculated, or derived element areas, according to anembodiment of the invention and where the fixed layout component isdisplayed as a component of an overall display 102, 106, 107, 108, 109(referring to FIG. 1A and FIG. 1B). Some of the variables rules metadatalogic 807 (referring to FIG. 8B) may be associated with the fixed areadisplayed element areas.

According to the embodiment, on initialization of the overallprogrammatic user interface 103 (referring to FIG. 1A) and 110(referring to FIG. 1B) and the embedded fixed-layout components 102,106, 107, 108, 109 (Referring to FIG. 1A and FIG. 1B) a dynamicexecution of at least a portion of the variables rules logic may becompleted. This may result in some rules variables data values beinggenerated/calculated or set and being displayed (referring to FIG. 18K)18116, 18109. The variables rules data value 18116 may be associatedwith element area 18102 or 18103 and variable rules variable label 1804.The variables rules data value 18109 may be associated with element area18108 or 18110 and variable rules variable label 18107;

The process starts at step (referring to FIG. 29 ) 2910 by loading afixed layout component onto a display screen of a user device 2401 a,upon receiving a request from user device 2401 a. The fixed-layoutprocessor 2805 may display for each element area it may have found orderived element areas in an initial display state. An embodiment of theinitial display state for element areas, (referring again FIG. 18K)would be that the found 18102 or derived 18103 element area may displaythe relevant element area but with no overall value data 18116 comprisedwithin, i.e., data 18116 would display in its initial state as blank asit is not yet calculated. Similarly found area 18108 or derived elementarea 18110 would display the relevant element area but with no overallvalue data 18109 comprised within; i.e. the data 18109 would display asblank in its initial state as it is not yet calculated.

Each fixed-layout component package 806 may comprise a set of associatedvariables logic rules 807 (referring to FIG. 8A) to determine how toautomatically process and generate variables data, and where somevariables rules (and associated data) can be directly associated withspecific element areas (referring to FIG. 18K) 18116, 18109.

The data variables with an association for a user element areainteraction may be termed user requested variables (URV). User requestedvariables (URV's) may then support the calculation of derived variables(DV's), and on the calculation of at least a portion of derivedvariables, then derived-variable-labels (DVL's) may be generated fromuser (URV) and derived (DV) variables or other derived variable labels(DVL) and/or set variables (SVs). Set variables can also support thecalculation of all variable types.

On completion of loading of the overall fixed-layout component 2910, thenext step 2902 will then load the associated variables rules meta data807 via 806 (referring to FIG. 18J) into the variable's rules processor2807 (referring to FIG. 28 ). The variables rules processor 2807 willthen dynamically process all the variables rules meta data logic. Somevariables rules may be associated with specific element areas(found/calculated or derived), and where the programmatic user interfacemay then present to the user device, those variables rules which mayrequire a user interactivity via a user device 2401 a (e.g. variablerule type: user requested variable: URV). A set variable (SV) rule typecan display e.g. the START data value 18123 (referring to FIG. 18A).

On completion of at least a portion of user inputs variables rules (e.g.user requested variables: URV) from user device 2401 a and combined withany relevant set variables, the variables rules processor 2807 willcommence a process to automatically generate at least a portion ofderived variable values: at step 2903 the rules meta data processor 2807will process the first rule 2903 to generate the first derived valuedata item. The variables rules processor 2807 will then load and processat least a portion of derived variables rules at step 2905 and iterate2904 through all of the associated variables rules until completed. Oncompletion of steps 2903, 2905, 2904, the variables rules processor 2807will then commence processing of the first derived variable label rule(utilizing the user variable data items and also other derived variablesdata items and set variables where applicable as inputs). The variablesrules processor 2807 will iteratively process at least a portion ofderived variable label rules 2908, 2907 until the at least portion ofrules are processed. The variable rules processor 2807 may save at leasta portion of the variables data (as outputs from the at least portion ofrules processing) to the fixed-content user data store 1313 or the userapp data store 1407. As a final step 2909 the fixed layout processor2805 will then refresh the display areas (found or derived) for at leasta portion of fixed-layout element areas and where the variable datavalues are then displayed by using the logical association element areainteractivity association meta data 803. The fixed layout processor 2805will utilize the element area interactivity association meta data 803 tolink which user variable value, derived variable value, and derivedvariable label values to each specific element area (found or derived)for display purposes. An element area may display no data value, or adata value, and that data value might be from a user variable valuedata, or a derived variable value data, or a derived variable labelvalue data.

Hardware Architecture

Generally, the techniques disclosed herein may be implemented onhardware or a combination of software and hardware. For example, theymay be implemented in an operating system kernel, in a separate userprocess, in a library package bound into network applications, on aspecially constructed machine, on an application-specific integratedcircuit (ASIC), or on a network interface card.

Software/hardware hybrid implementations of at least some of theembodiments disclosed herein may be implemented on a programmablenetwork-resident machine (which should be understood to includeintermittently connected network-aware machines) selectively activatedor reconfigured by a computer program stored in memory. Such networkdevices may have multiple network interfaces that may be configured ordesigned to utilize different types of network communication protocols.A general architecture for some of the machines may be described hereinin order to illustrate one or more exemplary means by which a given unitof functionality may be implemented. According to specific embodiments,at least some of the features or functionalities of the variousembodiments disclosed herein may be implemented on one or moregeneral-purpose computers associated with one or more networks, such asfor example an end-user computer system, a client computer, a networkserver or other server system, a mobile computing device (e.g., tabletcomputing device, mobile phone, smartphone, laptop, or other appropriatecomputing device), a consumer electronic device, a music player, or anyother suitable electronic device, router, switch, or other suitabledevice, or any combination thereof. In at least some embodiments, atleast some of the features or functionalities of the various embodimentsdisclosed herein may be implemented in one or more virtualized computingenvironments (e.g., network computing clouds, virtual machines hosted onone or more physical computing machines, or other appropriate virtualenvironments).

FIG. 17A illustrates an example of a conventional system bus computingarchitecture system 1700, and where the components are in electricalcommunication with each other using a bus 1707. The exemplary system1700 includes a processor unit 1708 and the system bus 1707 thatconnects the various items: memory 1701, RAM 1702, ROM 1703 to theprocessor 1708. The system processor 1708 may be supported by cache 1709performant memory or be integrated as part of the processor 1708. Thesystem 1700 may copy data from the memory 1701 and/or the storage device1710 to the cache 1709 for rapid access by the processor 1708. Cache mayprovide performance, rather than having the processor 1708 waiting fordata. These and other modules may control or be configured to controlthe processor 1708 to perform certain actions, and which may require theuse of memory 1701. The memory may consist of many different types andperformance characteristics. The processor 1708 may include ageneral-purpose component, or hardware or software modules, such asmodules 1711, 1712, stored in the storage device 1710, and configured tocontrol the processor 1708 as well as any special purpose processorwhere software instructions are incorporated into the actual processordesign. The processor 1708 may be a self-contained computing comprisingmultiple processors or cores, bus, memory controller, and cache etc. Theuser interaction 1704 with the device may be any number of mechanisms,such as keyboard, mouse, a touch-sensitive screen for gesture orgraphical input or other. The output-device 1705 may be display screen.The communications interface 1706 may typically govern and manage theuser input and system output. There is no restriction on operating onany particular hardware arrangement and therefore the basic featureshere may easily be substituted for improved hardware or firmware as theyare developed. The storage device 1710 is non-volatile memory may be ahard disk or other types of nontransitory computer readable media whichmay store data that is accessible by a computing device, such assolid-state memory device, flash memory, read only memory 1703 ROM.

FIG. 17B illustrates an example computer system 1715 which has a chipsetarchitecture that could be used to execute the described system andmethods and managing the graphical user interfaces on the devices.Computer system 1715 is an example of computer hardware, software andfirmware that may be used to implement the disclosed technology. Thesystem 1715 may include a processor 1717 representing any number ofphysically and/or logically distinct resources capable of executingsoftware, firmware and hardware configured to perform identified logiccomputations. The processor 1717 may communicate with a chipset 1716which in turn may control inputs to/from the processor 1717, outputs tothe output device 1721 and may read/write information to the storagedevice 1719 which may include any number of media types including forexample solid state media. Chipset 1717 may also read/write to the RAM1718 module. A chipset processor 1717 may output information to outputs1721 such as a device display and may read/write information to astorage device 1719, which may include may media types, including solidstate media. Chipset 1717 may also read/write data to RAM 1718. Chipsetmay interface directly or indirectly with the output device 1721, andwhich could include a keyboard, a pointing device such as a mouse, or atouch-sensitive screen for gesture or graphical input. Inputs to thesystem 1715 may come from a variety of sources, human interface devicesand/or machine generated. Chipset 1717 may interface with one or morecommunications interfaces 1720 that may have different physicalinterfaces. Such communications interfaces may include interface forwired and wireless local or wide area networks. Some applications of themethods for generating, displaying, and using a GUI (graphical userinterface) disclosed herein may include receiving ordered informationdata over the physical interface or be generated by the processor 1717by analyzing data in the data storage 1719.

It may be appreciated that exemplary systems 1700, 1715 may have morethan one processor or be part of a group or cluster of computing devicesnetworked together to provide greater computing capability. For clarityof explanation in some instances the present technology may be presentedas including individual functional blocks comprising devices, devicecomponents, steps or routines in a method embodies in software, orcombinations of hardware and software.

Methods according to the above described examples may be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions may comprisefor example, instructions and data which cause or otherwise configure ageneral-purpose computer, special purpose computer or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resource used may be available over acommunications network. The computer executable instructions may be, forexample binaries, other intermediate format instructions such asassembly language, firmware or source code. Examples ofcomputer-readable media that may be used to store instructions,information used, and/or information created during methods according todescribed examples include flash memory, USB devices comprisingnon-volatile memory, networked storage devices etc.

Devices implementing methods according to those disclosures may comprisehardware, firmware, and/or software may take a variety of form factors.Form factor examples may include laptops, smart phones, personal digitalassistants, small factor personal computers etc. Functionality describedherein may also be embodied in peripherals. Such functionality may alsobe implemented on a circuit board among different chips or differentprocesses executing in a single device etc.

A variety of examples and other information was used to explain aspectswithin the scope of the disclosed methods, no limitations should beimplied based on particular features or arrangements in such examples,as one of ordinary skill would be able to use these examples to derive awide variety for implementations.

Referring now to FIG. 20 , there is shown a block diagram depicting anexemplary computing device 10 suitable for implementing at least aportion of the features or functionalities disclosed herein. Computingdevice 10 may be, for example, any one of the computing machines listedin the previous paragraph, or indeed any other electronic device capableof executing software- or hardware-based instructions according to oneor more programs stored in memory. Computing device 10 may be configuredto communicate with a plurality of other computing devices, such asclients or servers, over communications networks such as a wide areanetwork a metropolitan area network, a local area network, a wirelessnetwork, the Internet, or any other network, using known protocols forsuch communication, whether wireless or wired.

In one aspect, computing device 10 includes one or more centralprocessing units (CPU) 12, one or more interfaces 15, and one or morebusses 14 (such as a peripheral component interconnect (PCI) bus). Whenacting under the control of appropriate software or firmware, CPU 12 maybe responsible for implementing specific functions associated with thefunctions of a specifically configured computing device or machine. Forexample, in at least one aspect, a computing device 10 may be configuredor designed to function as a server system utilizing CPU 12, localmemory 11 and/or remote memory 16, and interface(s) 15. In at least oneaspect, CPU 12 may be caused to perform one or more of the differenttypes of functions and/or operations under the control of softwaremodules or components, which for example, may include an operatingsystem and any appropriate applications software, drivers, and the like.

CPU 12 may include one or more processors 13 such as, for example, aprocessor from one of the Intel, ARM, Qualcomm, and AMD families ofmicroprocessors. In some aspects, processors 13 may include speciallydesigned hardware such as application-specific integrated circuits(ASICs), electrically erasable programmable read-only memories(EEPROMs), field-programmable gate arrays (FPGAs), and so forth, forcontrolling operations of computing device 10. In a particular aspect, alocal memory 11 (such as non-volatile random-access memory (RAM) and/orread-only memory (ROM), including for example one or more levels ofcached memory) may also form part of CPU 12. However, there are manyways in which memory may be coupled to system 10. Memory 11 may be usedfor a variety of purposes such as, for example, caching and/or storingdata, programming instructions, and the like. It should be furtherappreciated that CPU 12 may be one of a variety of system-on-a-chip(SOC) type hardware that may include additional hardware such as memoryor graphics processing chips, such as a QUALCOMM SNAPDRAGON™ or SAMSUNGEXYNOS™ CPU as are becoming increasingly common in the art, such as foruse in mobile devices or integrated devices.

As used herein, the term processor is not limited merely to thoseintegrated circuits referred to in the art as a processor, a mobileprocessor, or a microprocessor, but broadly refers to a microcontroller,a microcomputer, a programmable logic controller, anapplication-specific integrated circuit, and any other programmablecircuit.

In one aspect, interfaces 15 are provided as network interface cards(NICs). Generally, NICs control the sending and receiving of datapackets over a computer network; other types of interfaces 15 may forexample support other peripherals used with computing device 10. Amongthe interfaces that may be provided are Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces,graphics interfaces, and the like. In addition, various types ofinterfaces may be provided such as, for example, universal serial bus(USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT′, PCI, parallel, radiofrequency (RF), BLUETOOTH™, near-field communications (e.g., usingnear-field magnetics), 802.11 (Wi-Fi), frame relay, TCP/IP, ISDN, fastEthernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) orexternal SATA (ESATA) interfaces, high-definition multimedia interface(HDMI), digital visual interface (DVI), analog or digital audiointerfaces, asynchronous transfer mode (ATM) interfaces, high-speedserial interface (HSSI) interfaces, Point of Sale (POS) interfaces,fiber data distributed interfaces (FDDIs), and the like. Generally, suchinterfaces 15 may include physical ports appropriate for communicationwith appropriate media. In some cases, they may also include anindependent processor (such as a dedicated audio or video processor, asis common in the art for high-fidelity A/V hardware interfaces) and, insome instances, volatile and/or non-volatile memory (e.g., RAM).

Although the system shown in FIG. 20 illustrates one specificarchitecture for a computing device 10 for implementing one or more ofthe aspects described herein, it is by no means the only devicearchitecture on which at least a portion of the features and techniquesdescribed herein may be implemented. For example, architectures havingone or any number of processors 13 may be used, and such processors 13may be present in a single device or distributed among any number ofdevices. In one aspect, a single processor 13 may handle communicationsas well as routing computations, while in other aspects a separatededicated communications processor may be provided. In various aspects,different types of features or functionalities may be implemented in asystem according to the aspect that includes a client device (such as atablet device or smartphone running client software) and server systems(such as a server system described in more detail below).

Regardless of network device configuration, the system of an aspect mayemploy one or more memories or memory modules (such as, for example,remote memory block 16 and local memory 11) configured to store data,program instructions for the general-purpose network operations, orother information relating to the functionality of the aspects describedherein (or any combinations of the above). Program instructions maycontrol execution of or comprise an operating system and/or one or moreapplications, for example. Memory 16 or memories 11, 16 may also beconfigured to store data structures, configuration data, encryptiondata, historical system operations information, or any other specific orgeneric non-program information described herein.

Because such information and program instructions may be employed toimplement one or more systems or methods described herein, at least somenetwork device aspects may include nontransitory machine-readablestorage media, which, for example, may be configured or designed tostore program instructions, state information, and the like forperforming various operations described herein. Examples of suchnontransitory machine-readable storage media include, but are notlimited to, magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks, and hardware devices that are speciallyconfigured to store and perform program instructions, such as read-onlymemory devices (ROM), flash memory (as is common in mobile devices andintegrated systems), solid state drives (SSD) and hybrid SSD storagedrives that may combine physical components of solid state and hard diskdrives in a single hardware device (as are becoming increasingly commonin the art with regard to personal computers), memristor memory, randomaccess memory (RAM), and the like. It should be appreciated that suchstorage means may be integral and non-removable (such as RAM hardwaremodules that may be soldered onto a motherboard or otherwise integratedinto an electronic device), or they may be removable such as swappableflash memory modules (such as thumb drives or other removable mediadesigned for rapidly exchanging physical storage devices), hot-swappablehard disk drives or solid state drives, removable optical storage discs,or other such removable media, and that such integral and removablestorage media may be utilized interchangeably. Examples of programinstructions include both object code, such as may be produced by acompiler, machine code, such as may be produced by an assembler or alinker, byte code, such as may be generated by for example a JAVA™compiler and may be executed using a Java virtual machine or equivalent,or files comprising higher level code that may be executed by thecomputer using an interpreter (for example, scripts written in Python,Perl, Ruby, Groovy, or any other scripting language).

In some embodiments, systems may be implemented on a standalonecomputing system. Referring now to FIG. 21 , there is shown a blockdiagram depicting a typical exemplary architecture of one or moreaspects or components thereof on a standalone computing system.Computing device 20 includes processors 21 that may run software thatcarry out one or more functions or applications of aspects, such as forexample a client application 24. Processors 21 may carry out computinginstructions under control of an operating system 22 such as, forexample, a version of MICROSOFT WINDOWS™ operating system, APPLE macOS™or iOS™ operating systems, some variety of the Linux operating system,ANDROID™ operating system, or the like. In many cases, one or moreshared services 23 may be operable in system 20 and may be useful forproviding common services to client applications 24. Services 23 may forexample be WINDOWS™ services, user-space common services in a Linuxenvironment, or any other type of common service architecture used withoperating system 21. Input devices 28 may be of any type suitable forreceiving user input, including for example a keyboard, touchscreen,microphone (for example, for voice input), mouse, touchpad, trackball,or any combination thereof. Output devices 27 may be of any typesuitable for providing output to one or more users, whether remote orlocal to system 20, and may include for example one or more screens forvisual output, speakers, printers, or any combination thereof. Memory 25may be random-access memory having any structure and architecture knownin the art, for use by processors 21, for example to run software.Storage devices 26 may be any magnetic, optical, mechanical, memristor,or electrical storage device for storage of data in digital form (suchas those described above, referring to FIG. 20 ). Examples of storagedevices 26 include flash memory, magnetic hard drive, CD-ROM, and/or thelike.

In some embodiments, systems may be implemented on a distributedcomputing network, such as one having any number of clients and/orservers. Referring now to FIG. 22 , there is shown a block diagramdepicting an exemplary architecture 30 for implementing at least aportion of a system according to one aspect on a distributed computingnetwork. According to the aspect, any number of clients 33 may beprovided. Each client 33 may run software for implementing client-sideportions of a system; clients may comprise a system 20 such as thatillustrated in FIG. 21 . In addition, any number of servers 32 may beprovided for handling requests received from one or more clients 33.Clients 33 and servers 32 may communicate with one another via one ormore electronic networks 31, which may be in various aspects any of theInternet, a wide area network, a mobile telephony network (such as CDMAor GSM cellular networks), a wireless network (such as Wi-Fi, WiMAX,LTE, and so forth), or a local area network (or indeed any networktopology known in the art; the aspect does not prefer any one networktopology over any other). Networks 31 may be implemented using any knownnetwork protocols, including for example wired and/or wirelessprotocols.

In addition, in some embodiments, servers 32 may call external services37 when needed to obtain additional information, or to refer toadditional data concerning a particular call. Communications withexternal services 37 may take place, for example, via one or morenetworks 31. In various aspects, external services 37 may compriseweb-enabled services or functionality related to or installed on thehardware device itself. For example, in one aspect where clientapplications 24 are implemented on a smartphone or other electronicdevice, client applications 24 may obtain information stored in a serversystem 32 in the cloud or on an external service 37 deployed on one ormore of a particular enterprise's or user's premises.

In some embodiments, clients 33 or servers 32 (or both) may make use ofone or more specialized services or appliances that may be deployedlocally or remotely across one or more networks 31. For example, one ormore databases 34 may be used or referred to by one or more aspects. Itshould be understood by one having ordinary skill in the art thatdatabases 34 may be arranged in a wide variety of architectures andusing a wide variety of data access and manipulation means. For example,in various aspects one or more databases 34 may comprise a relationaldatabase system using a structured query language (SQL), while othersmay comprise an alternative data storage technology such as thosereferred to in the art as NoSQL (for example, HADOOP CASSANDRA™, GOOGLEBIGTABLE™, and so forth). In some embodiments, variant databasearchitectures such as column-oriented databases, in-memory databases,clustered databases, distributed databases, or even flat file datarepositories may be used according to the aspect. It will be appreciatedby one having ordinary skill in the art that any combination of known orfuture database technologies may be used as appropriate, unless aspecific database technology or a specific arrangement of components isspecified for a particular aspect described herein. Moreover, it shouldbe appreciated that the term database as used herein may refer to aphysical database machine, a cluster of machines acting as a singledatabase system, or a logical database within an overall databasemanagement system. Unless a specific meaning is specified for a givenuse of the term database, it should be construed to mean as a plainmeaning of the term database by those having ordinary skill in the art.

Similarly, some aspects may make use of one or more security systems 36and configuration systems 35. Security and configuration management arecommon information technology (IT) and web functions, and some amount ofeach are generally associated with any IT or web systems. It should beunderstood by one having ordinary skill in the art that anyconfiguration or security subsystems known in the art now or in thefuture may be used in conjunction with aspects without limitation,unless a specific security 36 or configuration system 35 or approach isspecifically required by the description of any specific aspect.

FIG. 23 shows an exemplary overview of a computer system 40 as may beused in any of the various locations throughout the system. It isexemplary of any computer that may execute code to process data. Variousmodifications and changes may be made to computer system 40 withoutdeparting from the broader scope of the system and method disclosedherein. Central processor unit (CPU) 41 is connected to bus 42, to whichbus is also connected memory 43, nonvolatile memory 44, display 47,input/output (I/O) unit 48, and network interface card (NIC) 53. I/Ounit 48 may, typically, be connected to keyboard 49, pointing device 50,hard disk 52, and real-time clock 51. NIC 53 connects to network 54,which may be the Internet or a local network, which local network may ormay not have connections to the Internet. Also shown as part of system40 is power supply unit 45 connected, in this example, to a mainalternating current (AC) supply 46. Not shown are batteries that couldbe present, and many other devices and modifications that are well knownbut are not applicable to the specific novel functions of the currentsystem and method disclosed herein. It should be appreciated that atleast a portion of components illustrated may be combined, such as invarious integrated applications, for example Qualcomm or Samsungsystem-on-a-chip (SOC) devices, or whenever it may be appropriate tocombine multiple capabilities or functions into a single hardware device(for instance, in mobile devices such as smartphones, video gameconsoles, in-vehicle computer systems such as navigation or multimediasystems in automobiles, or other integrated hardware devices).

In various aspects, functionality for implementing systems or methods ofvarious aspects may be distributed among any number of client and/orserver components. For example, various software modules may beimplemented for performing various functions in connection with thesystem of any particular aspect, and such modules may be variouslyimplemented to run on server and/or client components.

The skilled person will be aware of a range of possible modifications ofthe various embodiments described above. Accordingly, the presentinvention is defined by the claims and their equivalents.

What is claimed is:
 1. A system for intelligent layering of interactiveprogrammatic derived elements for fixed content, the system comprising:an intelligent layering computer comprising at least a processor, amemory, and a plurality of programming instructions stored in the memoryand operating on the processor, the programming instructions, whenexecuted by the processor, cause the processor to: receive a pluralityof configuration search logic for a plurality of found element areas;receive a search start position from the first user device, the searchstart position identifying a position with respect to a found elementarea; determine, based on the plurality of configuration search logic,element-area internal search directions from the search start positionwith respect to the found element area; calculate the found element areausing the element-area internal search directions; receive, from thefirst user device, data variable rules associated with the found elementarea; calculate a derived element area with respect to the found elementarea based on the data variable rules, wherein the derived element areacomprises a percentage, or proportion, of the found element area;position the derived element area relative to the found element area;and create a fixed-layout package comprising the plurality of foundelement areas, and the plurality of derived element areas as one or morelayers.
 2. The system of claim 1, wherein the plurality of programminginstructions when executed by the processor further cause the processorto calculate a plurality of derived element positions of the derivedelement area based on a plurality of incremental positions.
 3. Thesystem of claim 2, wherein the plurality of programming instructionswhen executed by the processor further cause the processor to: store aset of coordinates identifying the search start position; detect anassociated pixel color at a first location coordinate; compare theassociated pixel color at the first location coordinate with pixel colordetected at a first incremental position of the plurality of incrementalpositions; and calculate a derived element position of the plurality ofderived element positions based on the comparison.
 4. The system ofclaim 1, wherein the plurality of programming instructions when executedby the processor further cause the processor to apply one or moreadjustments to each found element area of the plurality of found elementareas.
 5. The system of claim 4, wherein for each found element area ofthe plurality of found element areas, the one or more adjustments arebased on a width or a height, dimensions, relative position, or acombination thereof, of the found element area.
 6. The system of claim1, wherein the plurality of programming instructions when executed bythe processor further cause the processor to define a plurality ofparameters, each determining presentation of the plurality of derivedelement areas on a user interface of a display of the user device andbehavior of an interaction of the user device with the plurality ofderived element areas.
 7. A method for intelligent layering ofinteractive programmatic derived elements for fixed content, the methodcomprising: receiving, from a first user device, a plurality ofconfiguration search logic for a plurality of found element areas;receiving, from the first user device, a search start position, thesearch start position identifying a position with respect to a foundelement area; determining, by an element finder, based on the pluralityof configuration search logic, element-area internal search directionsfrom the search start position with respect to the found element area;calculating, at the element finder, the found element area using theelement-area internal search directions; calculating, at the elementfinder, a derived element area with respect to the found element areabased on one or more data variable rules, wherein the derived elementarea comprises a percentage, or proportion, of the found element area;positioning, at the element finder, the derived element area relative tothe found element area; and creating, at an export manager, afixed-layout package comprising the plurality found element areas, andthe plurality of derived element areas as one or more layers.
 8. Themethod of claim 7, further comprising calculating a plurality of derivedelement positions based on a plurality of incremental positions of thederived element area.
 9. The method of claim 8, further comprising:storing, by the element finder, coordinates identifying the search startposition; detecting, by the element finder, an associated pixel color ata first location coordinate; comparing, by the element finder, theassociated pixel color at the first location coordinate with pixel colordetected at a first incremental position of the plurality of incrementalpositions; and calculating, by the element finder, a derived elementposition of the plurality of derived element positions based on thecomparison.
 10. The method of claim 7, further comprising applying, bythe element finder, one or more adjustments to a found element area ofthe plurality of found element areas.
 11. The method of claim 10,wherein for each found element area of the plurality of found elementareas, the one or more adjustments are based on a width or a height,dimensions, relative position, or a combination thereof, of the foundelement area.
 12. The method of claim 7, further comprising defining, bythe element finder, a plurality of parameters, each determiningpresentation of the plurality of derived element areas on a userinterface of a display of the user device and behavior of an interactionof the user device with the plurality of derived element areas.